Hmm. I have to believe that this is coming from something completely unrelated to CPTUI, but because it’s occurring, it’s breaking our functionality.
Are you familiar with editing your wp-config.php file at all? I’m asking cause I’m curious what more details we can extract with something like the SCRIPT_DEBUG constant being set, so that the WP admin would not use the combined/minified copies of javascript. This would allow for better tracking down exactly where the error is stemming from and what plugin/theme/file is triggering the error.
Hi! Thanks for the quick reply.
I did define script_debug to be true on my wp-config: https://www.screencast.com/t/HP9cQaaC
Tried again, and couldn’t see any new info or error really: https://www.screencast.com/t/OWjg3pnSjZ .
I even checked the php logs just in case, but those go 200 as well, and looks good. https://www.screencast.com/t/HtgSwijOj
I will try some plugin/theme isolation testing just to see if one of them is causing this, but if you have any other ideas, just let me know. THANKS!
yeah the isolation testing is the best I can suggest at this point. Start eliminating one by one until the issue goes away.
We don’t have any fancy JS going on outside of some light jQuery to handle some details, so I’m really curious at this point about the source of that error you’re seeing.
Hi! Just wanted to report. It is a conflict with an old plugin named “WP Advanced Comment”. Deactivating that plugin solves the issue, and I can edit CPTs fine.
I think its most possibly the other plugin’s fault as it is a bit of an old one, but I think you guys might want to know about it, as it interferes with CPTUI, and not my other plugins apparently.
Anyway thanks for the help and quick responses!
Good to know, and thank you for the followup information regarding the issue.
Have a good rest of your day 😀
