Bug When Editing Comments in Course Lessons
Hello! I noticed a bug in the course lessons. When a user leaves a comment and later tries to edit it, an error message appears, preventing them from doing so. Attached is a screenshot of the error.
Did you configure CDN?
olla Yes, the media is set up on BunnyCDN. Does this have anything to do with editing comments?
Elisa Faria offloading media is fine. But I faced issues with bunny acceleration CDN. This message it was between many.
https://community.wpmanageninja.com/portal/space/community-meta/post/cdn-accelerator
olla I tried disabling the Bunny CDN and switched back to local media, but the comment issue persists. By the way, I have a community running on a ".dev" domain for testing, clean, freshly installed, and practically with nothing configured – not even the CDN – and the comment editing issue is also present there. It seems like a bug in the version itself.
I noticed a few more things while running new tests: users with the Administrator role do not face the issue of editing comments. Only users with the Subscriber role. And only in COURSES. In spaces, editing works.
Elisa Faria I suspect it has to do with the cache. Apparently it is disabled for the administrator.
Artur Abakarov I am not using any cache plugin. Would it be a type of cache configured within the plugin itself? If so, how can I manage its behavior?
Elisa Faria can't say for sure as you need to dive deeper. But if there is no plugin, try clearing your browser cache or logging in incogneto mode. If that doesn't help, you should write a ticket.
Artur Abakarov Well... These things are not solving the issue. I have already uninstalled all plugins to avoid conflicts, switched to the default theme, cleared the cache at all possible levels, and tried several new server configurations.
I have just opened a ticket with the team because the error is getting worse, now preventing me from deleting courses as well.
Thank you for your help!
Elisa Faria sounds like something not nice, you need to look deeper with this one. Good luck!
We are on it.
Just to let you know, We have fixed the issue on our dev branch. We will ship it in the next version.