Unable To Update Or Create New Pages/Posts With Classic Editor Since Update

  • Updated to 5.1.1 and Block Editor really messes up my html and websites layouts when I try to update so I installed the Classic Editor Plugin. The problem is when I try to update a webpage with the Classic Editor is it just redirects to the homepage of the website and doesn’t save the update. The only way I can update is by using the Block Editor which, as I stated, messes up the layout by adding or removing important elements.

    What’s even weirder is if I copy and paste a template code that I use for posting weekly articles into a brand new post using Classic Editor it does the same thing.

    So not only can I not make updates to an existing page or post using the Classic Editor I also cannot paste html into the Classic Editor and create a new page or post. If I add a new page or post and simply type something using the Classic Editor it will save but I can’t add html. Very strange.

    Here’s a video that might help to better explain when setting up a new post… https://getsmarthomedevices.com/New-Post-Classic-Editor.mov

    Here’s a video showing if I try to update an existing page in the Classic Editor… https://getsmarthomedevices.com/Updating-Post-Classic-Editor.mov

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Andrew Ozz

    (@azaozz)

    Looks like a plugin is redirecting on saving the form based on the post content… Thinking you will have to disable plugins one by one until you find which is doing it, then contact the author for a fix. Very strange, indeed, plugins shouldn’t be doing this kind of redirecting…

    I am experiencing a similar issue. With the latest WP version and latest version Classic Editor, whenever I try to update a page that contains the embed code for my newsletter subscription (which is CSS/HTML/javascript and USED to work just fine), I get a 501 error. If I disable the Classic editor, then I can update pages with that newsletter code just fine. I’m not trying to modify the form code, just edit anything in the text/visual tab and I can’t preview or save my changes UNLESS I turn off the classic editor. I’m not sure what could be causing that.

    Plugin Author Andrew Ozz

    (@azaozz)

    @creativecaro hmm, strange. This suggests that the “old” way of saving a post (posting the form data to wp-admin/post.php) fails for some reason. Don’t think there were any changes in WP 5.2 that can cause it to fail (will look more there).

    As you are getting HTTP 501 “not implemented” errors, guessing they may be coming from some changes/settings on the server? Could you contact your hosting company and ask them to have a look what is throwing these errors please.

    @azaozz, thanks for the reply. I’ve been in contact with the hosting (bluehost) and the case has escalated, but no reply from them yet as to what could be causing the problem. I kept troubleshooting on my own when I noticed that turning off Classic Editor enabled me to save the code in a post (but NOT in a custom field – so turning off Classic Editor did NOT fix the issue entirely.), so I figured I’d try to find other reports of similar occurrences, which led me here. It’s not javascript per se that is throwing the error because I can successfully create a “Hello World” alert. The embed code (SS/HTML/JS is quite long, so I have no idea if perhaps I’m hitting some sort of a limit with what can be saved in the database, but it would be weird for that limit to suddenly change. So I’m stumped (and waiting to hear back from bluehost). Perhaps it’s something in the latest release of 5.2 where they’ve increased the security of something or other. I tested downgrading to 4.9.8 and the issue remained (but perhaps some database changes stayed in place).

    Plugin Author Andrew Ozz

    (@azaozz)

    @creativecaro yeah, I’m pretty sure this is not caused by the Classic Editor plugin directly, but rather by using the classic editor in WP.

    The embed code (SS/HTML/JS is quite long, so I have no idea if perhaps I’m hitting some sort of a limit…

    …

    I tested downgrading to 4.9.8 and the issue remained

    Yes, sounds like some part/string in that embedded core is triggering some “security flags” on the server when posting through a standard POST request (i.e. from the old Edit Post screen), but not when posting through the REST API (from the block editor). Could possibly be caused by differences in the encoding of the post content.

    I’m sure Bluehost will find and fix it. Would be good to get to the bottom of this and prevent it in the future.

    @azaozz, thanks so much for your input. I’m still waiting to hear back from bluehost. If I ever find out, I’ll report back.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Unable To Update Or Create New Pages/Posts With Classic Editor Since Update’ is closed to new replies.