Please Make the Old Editor Discoverable
-
When the new editor is still, after so many months, stubbornly unusable insofar as categories go, I’m baffled by WordPress’s almost militant insistence that we nonetheless use the new editor?
Why?
I’ve found a manual way to redirect to the old editor, but being forced to do so in such a roundabout way doesn’t engender any good feelings.
Maybe WordPress, et al, is sick of reading posts like these, but I’m fed up with the new editor as are, apparently, many others.
The blog I need help with is: (visible only to logged in users)
-
Sharon here, from the ’11sixtynine’ blog, Ireland – I’m having constant trouble with the new HTML Editor and would much prefer to have the old editor back, or at least to have the option to use it.
The new editor does not convert html into ‘readable’ content unless you change certain settings and those settings seem to change constantly?
Hoping for some help with this issue,
Thanks,
Sharon,
Dublin. -
If you click on ‘My Sites’ in the top left-hand corner then ‘WP Admin’ comes up in the left hand menu. This takes you to the old editor.
-
Do not expect an easy link to the good editor – the Blue Death Editor is the new holy grail of editors and WordPress.COM has embarked on a calculated scorched earth policy of making it hard to get to a good editor and forcing you to use the Blue Death Editor
-
//If you click on ‘My Sites’ in the top left-hand corner then ‘WP Admin’ comes up in the left hand menu. This takes you to the old editor. //
That’s not the issue. It is trivially and embarrassingly easy for WordPress to add an easily discoverable toggle to both editing windows, the classic editor and the BETA editor. They had one and removed it. Both editors have their advantages. The classic editor does *all* tasks well. The BETA editor does *some* tasks better, but some features are out and out unusable.
This is ridiculous.
Why is WordPress being so pig-headed about this? Do they think they’re Microsoft? Are they just going to shove their BETA “experience” down everyone’s throats? Is this a cynical decision? Have they decided we use the old editor only because we’re “used to it”? (And I’m quoting them, by the way.) Are the programmers taking this personally?!? Do they say to themselves: Well, we’ll just force them to use the BETA editor and they’ll get “used to it”.
There is no reason a toggle can’t be added. There are advantages to both editors. I can see bloggers switching between the two (and maybe only once or twice during the course of a post) until the BETA editor — and I can’t stress enough that it is still **BETA software** — is fully ready. It would be to their advantage.
From this blogger’s perspective, they’ve handled the transition, so far, with all the customer relations skills of a budding Comcast.
-
WordPress obviously doesn’t like the “classic” editor. It worked too well. Beep Beep Boop is now the default editor because it appeals to teen-age bloggers whose writings are no more complicated than Tweets, which they post using their IPhones. That’s the kind of blogger WordPress wants, because they don’t make much use of the servers with numerous drafts, the way most of the old-timers do. That’s the only explanation for why the classic editor is becoming increasingly difficult to find. I used to really like WordPress, and when asked, I would recommend it. No longer. I regard it the way I do Google — I use it, but I don’t really care about it.
-
Personally, I like that WordPress is experimenting and attempting to improve; but none of the bugs that made the Beta editor unusable have been addressed. Even so, that doesn’t seem to stop them from ever more forcefully trying to shove it down our throats.
If this sort of behavior continues, I wouldn’t be surprised if WordPress simply decides to remove the mature editor. If that happens then I’ll have to move the blog. The Beta editor just doesn’t work. Frustrating.
-
I agree. There seems to be a move to dumb down functionality. The most recent one slipped in silently is the link editor (this applies to classic or blue editor)
When you add or edit a link there used to be an optional field for the ‘title’ – text placed here would appear when readers hovered over your link.
That’s now gone, and been replaced with ‘text’ which is just a copy of the text you highlighted in the editor (dumb!)
To add a hover link you need to edit the link in text mode – slow and frustrating – what is the benefit of this change?
-
I find the new editor quick and easy for simple posts but on my larger blogs with multiple posts I find it impossible to keep a handle on what is going on with the new editor. It is more like using a social platform than a serious blogging platform. Hopefully we will continue to get the choice.
-
You cannot deactivate the new Beep Beep Boop editor but you do not have to use it. For locating the ways and means of accessing the legacy or classic pages for creating posts, editing posts, and viewing stats see here > Navigating the Classic WordPress.COM interface http://onecoolsitebloggingtips.com/2015/04/05/navigating-the-classic-wordpress-com-interface/
Mar 18, 2015, 10:29 AM
The Classic Editor will continue to exist in wp-admin. We know some users prefer to use this editor, so we want you to have access to it, instead of phasing it out with the new version of the Dashboard. However, a link to the Classic Editor will not return to the New Editor. https://en.forums.wordpress.com/topic/when-editing-an-old-post-how-do-i-switch-to-the-classic-editor?replies=5Features that won’t be included in the new editor
Post Revisions
Copy a Post
Link back to wp-admin
Read more here https://en.forums.wordpress.com/topic/please-reinstate-the-option-of-choice-to-use-the-old-publishing-format/page/32?replies=942#post-2338964 -
Thanks for your input, but it doesn’t address the purpose of my post. Your link, by the way, is what I referred to when I mentioned finding “a manual way”.
//However, a link to the Classic Editor will not return to the New Editor.//
Says who? God? It’s this attitude that I’m writing about. There’s no reason a link to the Functional Editor can’t be re-introduced to the Beta Editor. It’s frankly baffling. Why does WP insist on forcing an inferior Beta quality product down everyone’s throat’s? How is this a good business decision? How is this a good programming decision?
Please make the old editor discoverable.
-
My input above consists of quoting Staff in earlier forum threads and your Says who? God? remark is out to lunch. There are many threads on this issue that were posted in March, which was when we WordPress.COM bloggers, who supported the return of the link to the classic editor to the Beep Beep Boop editor lost the battle. If you take the time to read this main thread https://en.forums.wordpress.com/topic/please-reinstate-the-option-of-choice-to-use-the-old-publishing-format?replies=942 and the others here that date back that far https://en.forums.wordpress.com/tags/new-editor-feedback then you will know that you are tilting at windmills.
You can also read the Staff post I linked to in my own.
The Classic Editor will not be removed from WordPress.com. However, many of the links will continue to point to the New Editor as we continue to increase your ability to manage your sites (self-hosted or not) straight from the WordPress.com interface. You can read a bit more about this plan here: One Central Hub for All Your Content
The new editor has been under development for 2 years now. Staff do not need to justify any decisions made by management when they are made, let alone months or years after they are made, and they said all they had to say months ago. :(
-
//Says who? God? remark is out to lunch.//
Thanks for the insult.
It would be one thing if in all that time (months and years you say) WordPress management and staff had offered a new and fully functional editor, but they haven’t. The bugs persist. It’s still Beta quality. So no. They can tell users to buzz off, but we’re still going to complain and with justification.
This is an ongoing problem.
- The topic ‘Please Make the Old Editor Discoverable’ is closed to new replies.
WordPress.com Forums 