Bookmarklet to force WordPress classic-editor
Posted by jpluimers on 2022/03/29
A while ago, WordPress.com heavily started to de-emphasise the Classic Editor in order to boost the Gutenberg editor which is bloaty (in both browser DOM usage (heavily slowing down editing) and content (lots of meta tags that are added to blog source) and is missing essential features (especially nesting of blocks often breaks things).
With 7000+ blog posts in the Classic Editor format (a few in still supported markdown format: that experiment failed horribly!) that still require editing (especially because of link rot)
So here is the Bookmarklet code to switch back an editing URL that you can use for as long as the Classic Editor is there:
javascript:location.href=document.location.href+'&classic-editor';
Yup, it is that simple: it appends &classic-editor to the URL.
Related:
- [Wayback] WordPress Classic Editor – EOL December 2021? – Hexagon Webworks
- [Wayback/Archive.is] Why does Gutenberg suck so fucking hard? : WordPress
- [Wayback] Classic Editor Lifespan – Support | Kriesi.at – Premium WordPress Themes
- [Wayback/Archive.is] Classic Editor (advanced view) – WordPress plugin | WordPress.org
Enables the previous “classic” editor and the old-style Edit Post screen with TinyMCE, Meta Boxes, etc. Supports all plugins that extend this screen.
- [Wayback] ClassicPress: The CMS for Creators | Instantly Familiar
ClassicPress is a community-led open source content management system. A fork of WordPress 4.9, it retains the WordPress classic editor as the default option.
- [Wayback] Classic Editor Lifespan – Support | Kriesi.at – Premium WordPress Themes
- [Wayback] Classic Editor – Support — WordPress.com
–jeroen
The Wiert Corner - irregular stream of stuff 
Leave a Reply