The fix really depends on what is causing the 500 error which is never one single source. I have to believe that chances are more that something being run in general in the post editor screen for this post type is the originating source. However, I don’t have any spot I can point to to say “oh it’s something over there”.
Any error logs that you can access or your hosting support can access and check on would be most helpful at this point. Oxygen builder here is a plugin, correct, not a theme? Not sure if you have any site copy available where you could disable it and see if the editor screen still errors in some way. Understood if you don’t, but it does leave the other side of the equation being that the error originates from their plugin.
Hi Michael. Thanks for the response
I will look into error logs for you.
Oxygen is a plugin, yep. It overrides the basic WP theme and functions.php functionality and funnels everything through the plugin. Normal plugins can work just fine with it, but I think if there are deprecated terms or some other small coding errors, it can cause this 500 error
I know it doesn’t happen on every page and up until recently, it didn’t happy on this page. It would lead me to believe that there was something in the new update that cause that. Would you be able to email me an older version of the plugin from a few weeks ago to see if that would solve the issue and perhaps get us on the right track?
Thanks very much for the assistance, mate 🙂
You can download older versions of CPTUI over at https://ww.wp.xz.cn/plugins/custom-post-type-ui/advanced/ with the dropdown at the end of the page.
Fun fact, you can do that with most plugins on .org here, at least as long as they use tagging with their releases.
Not sure there’s much that would affect this, for our releases in 2020, but stranger things have happened too.
