-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Panopto block settings page error #214
Comments
Hi @thebandesz,
However, please note that you gave a full screenshot in report, and the specific system can be identified easily, so giving exact versions of systems and plugins may be problematic, security-wise. |
If the problem is in this plugin's code, then I would look here:
The private |
Dear @acquaalta Since we are UpToDate with security patches i think i can share these. Hi @jrchamp I am not sure i understand what you said. Can you help me how do i get an actual error message with the line you quoted? Or since we are getting null it means the API causing the error? |
@thebandesz Please open up support ticket so we can take a deeper look into your specific case and determine the root cause. Thank you in advance. |
I am sorry, can you guide me where to open a support ticket, I thought this page had this purpose. |
Hן @thebandesz I'm NOT representative of Panopto or a maintainer of this plugin, but I guess that he means that you should send an e-mail to [email protected] or create a support ticket via another method that they offer in their support site. Even if this is an official plugin of Panopto, to the best of my knowledge the guys here are maintainers of the plugin, and not the support team of Panopto. It's common that companies want to track issues like that in their support system. |
Clicking block settiongs option causes: Exception - Call to a member function getMessage() on null)
Many users experiencing this error, we can't figure out what causes, it seems random. Even some admin user experiencing this error. We tried deleting a user, then resyncing, but the error remains. There is no difference between users. For some it works, for some it doesn't. Even Admins..
The text was updated successfully, but these errors were encountered: