Editor script v1.6.0
v1.6.0 of the classic editor redirect script is out! I may be very inactive on WordPress these days, but I’m still committed to providing updates to these scripts when they break. If something’s broken, please create a GitHub issue or let me know in the comments. Thanks to musicdoc1 for reporting again this time!
As usual, your script should have updated itself, but if not, you can head over to Greasy Fork and install it manually.
This change also affects the bookmarklet, so if you use the bookmarklet method, please replace it with the new version (delete the old one and re-add the new one). You can get the updated code on the workarounds page.
For the technical details, you can go look at commit bfe80e4. In the last week or so, WordPress.com has started redirecting classic wp-admin editor URLs to the new editor. The classic-editor query parameter is needed to prevent the redirect. Adding the new parameter was very simple, but more code was needed to prevent an infinite redirect loop. In a later commit, the code has also been reformatted and lightly refactored to make it look nicer.
I fear that this change means the classic editor is on its last legs and we may see it disappear altogether in the next change, so we should enjoy the classic editor while it’s still here.
If you have any troubles, please leave a comment and I’ll be happy to help you troubleshoot. Happy blogging!
`The Penguin' says... 
Thank you so much, Penguin! You are the best! And it works perfectly, too. I especially appreciate that when I click to Edit a published post it goes directly to the classic editor. Cheers! And hope you’ve been well, too.
I have indeed been well. Glad to hear it works for someone other than me. Enjoy, and I hope you’ve been well, too!
Yes, I’ve been well so far. Good to hear you have, too.
I actually used the “new” editor today thinking that the classic editor was no longer available. I used the “Classic” Block and it’s not terrible, but it is cluttered, imo. Had to click many times on the various settings on the sidebar to try to find basic things. From reading the comments on the WP Forums, it looks like the classic editor may be here only until Dec. 2021.
Sweeet! Thanks, tPenguinLTG! Wow, that was faster than it was reasonable to hope. Working like a charm. : )
I found that it didn’t work until I updated the script by clicking the “Check for userscript updates” item in the Tampermonkey menu.
Pingback: The Classic Editor Script Was Updated – Diary of Dennis
You know you did a great service to the community. And that several times. I informed my followers once again that you helped us out. Let’s see how much time it gives us. Yes, Automattic’s direction is clear, it’s very likely they will kill the old editor. Anyway, thank you once more!
You’re welcome once again! I hope someone will step up for the next solution. I noticed on your blog that you found a workaround that involves installing WordPress locally and it works, but it is a bit cumbersome (good on you for finding it!). We have a few options if a developer wants to step up:
Maintain a Web app that is based on the classic editor but communicates with the WP.com REST API client-side.
Maintain a Web app that is based on the classic editor but has a back-end component that communicates with the XML-RPC API.
Maintain a WordPress/ClassicPress plugin that allows a self-hosted or local WordPress instance to communicate with a remote instance via XML-RPC.
The second one isn’t worth doing since it’s basically the first one but less secure and double the effort. The third one is an interesting proposition and requires no maintenance of the classic editor, but is clunky for the user to set up. The first one should be the easiest to use as a user and would allow us to freely build in new features that are beneficial to the community, but I’m not sure how much of the existing editor code will be reusable.
I would have stepped up to build this myself, but unfortunately, I’m no longer as invested in WordPress as I used to nor do I have time to build or maintain such an application. I hope someone will step up, and if they do, I’m happy to bounce ideas around and provide a bit of help.
Yes, I had WordPress installed on localhost in the past, because I created a site for my self-employed uncle and his company at that time. So, I created everything offline and moved it to a hosting service once my uncle was happy…
So, that just came back to my mind recently. And I thought “Man, in the worst case, why don’t I just write content offline, and paste the HTML code into Gutenberg?”. Another possibility based on the same workaround is to write the drafts and upload the images to the offline blog. Maybe like writing posts in advance (5, 10, any number I like) and then use the export/import feature of WordPress. Then I could individually publish the drafts day by day on the live blog. Or set the post dates, so that they’re published automatically. But you’re right, it’s still more cumbersome.
Another idea I had was to make use of duplicator or site sync plugins. But the issue with this is that they usually require you not just to install the plugin on the localhost site but also on the live site. With that said, people would then need to get premium to be able to install plugins. But then they could basically install a Classic Editor plugin already too. So, duplicating or syncing with plugins makes no sense in our case.
The ideas you mentioned came to my mind too. Not technically explained and distinguished like you did but basically “Why are there no coders in the community that have come up with a web-based classic editor that connects with wordpress.com?”. In your case, I do understand it if you’re not fully invested here anymore. Honestly, you still helped us out a ton… like I said, can’t be appreciated enough. I am not kidding here, your script was excellent, and since the update, still is! You’ve done a great service already. I do understand, we move on with other things in life.
I am not a coder, sadly. But since I am geeky about PC stuff, I learned bits and bobs in all directions. Also coding… I learned a little bit of Visual Basic in the past, I then went through some basics of C++ and later C#, and more recently I watched Rust and Python videos on YouTube to find out if this is something for me. So, yeah, I am of no help yet. I just know how statements work, what variables and stuff are, and so on… I probably know far more than the average Joey, but not enough to call myself a programmer and go for such projects yet. I just never completed learning a language entirely, I am just trying to feature out if I can get into it. But the recent WordPress fiasco taught me that it’s maybe the time to step up my game and learn a language with persistence. Is there any language you would suggest for web-based stuff, especially based on your three ideas and the problems we have with WordPress (and personally, also in other cases, where web services changed, not to my liking and where I wish I could solve the problem with web-based applications in the future)?
For me, it’s probably too late now in the WordPress case since learning a language takes time. But as said, this is not the first time I dreamed of it or wished I’d be able to solve issues, with things that changed on the web. So, it’s probably time to learn something for the future. Maybe it’ll be handy for more than just that. So, I’d look into any of your suggestions. I liked the Python lessons a lot, not sure yet if this is a perfect fit for web-based apps.
Just a quick thought about your idea 3, with my little understanding about it, I am wondering… would that even work without installing some kind of listener plugin to the live site as well? Like in the case of those duplicators or sync plugins?
Oh, this is great! Thank you so much Penguin! I have dropped off my blogging very much in the last few months, but I wrote a few posts in the last couple of months. On Friday I opened the “add new post” page and almost fainted. The new editor!! I found the classic block, but I could not find the add media button, they have made it all so cumbersome. I do not understand why the powers that be in WordPress keep having to fix something that’s not broken.
By chance I found a work-around. I saved my post in draft in despair, and went back to the dashboard. At least that looks like the old thing. And then I opened the “posts” tab to edit my new post, and it opened in the original classic editor! I was astounded and delighted.
But now to be on the safe side i have installed your script and so far it seems to be working. Bravo and thank you again!