swmchau

Just managed to find out the metadata metaboxhidden_responsive_accordion which stores the hidden screen options. Deleting the table from the database solved the problem.
However, it’s still considered a bug somewhere as the case of no screen options is not handled. And also the plugin does not have a way to cleanup all related data after plugin deletion.

Exactly the same problem after updating to 2.1. There are 176 members.

Thanks for the fast and informative response. I managed to move the shortcodes to a separate page to isolate the issue. I disabled one optimizer plugin (Asset CleanUp Page Speed Booster) and the problem all of a sudden disappeared. I have 60 plugins and thankfully the right one was picked for the test. Interestingly, the problem only exhibits when the optimizer plugin is active (even after I disabled all its features), and when Motopress is invoked with 4 or more Photonic shortcodes.
So my solution is to simply disable the optimizer plugin and everything works perfectly.
Thanks for your efforts. The support is supreme … Simon

Wow, it works! Your support is amazing.
Thanks,
Simon

Same problem, and only occurs to one user. We are using all the latest versions (WordPress & UM)

That’s ok. I managed to use another special character for parsing to avoid the problem which is present in my mail client as well. Thanks anyway for the response.

Sorry, I just realized this was a different error message from a plugin I newly installed. I removed the plugin and now no more error. So your fix did worked for the previous error message. It’s a coincident of two similar error messages happening almost the same time.

The same problem is still there after updating the plugin. The update didn’t fix the issue.

I have two sites both giving the same message everytime plugin “MotoPress Content Editor Lite” is invoked to edit the contents. Clicking “x” can always close the error message window. The message is:
https://drive.google.com/file/d/1VRKPDU5jA52OmqUYclI-our-QGKdM4WK/view?usp=sharing

The problem started after I upgraded WordPress and all the plugins

Wordpress 5.2.1
PHP 7.1.29

Same error message brought me here.

Upgraded to PHP 7.1 and solved the problem … thanks

I have exactly the same error logs for lines 90 and 91. Not sure if it is related to the upgrade of WordPress to 5.1.1 recently.