WordPress Classic Editor disappears from Opera
-
raywood1 last edited by
I’ve been using the Tampermonkey script in Opera to compose and edit posts in Classic Editor on a non-plugin WordPress.com blog. Suddenly this morning the script is not working and the means of enabling Classic Editor seem to have disappeared.
I’m looking at an existing post in my blog. At the top of the screen, I select New > Post. That opens an empty post in the Gutenberg (block) editor. Normally, the script would fix that: I would get that new post in Classic Editor.
I go into the blog’s Settings > General > Admin Interface Style and choose Classic Style. That option is still there. But the next step advised by WordPress is to go to my list of posts (or pages) > mouse over a post > select Classic Editor. Here, again, the Classic Editor option is missing.
This seems to be something about Opera specifically. The script is still working in Firefox: new posts are opened in the Classic Editor. Even in Firefox, though, mousing over an existing post does not yield an option to select Classic Editor.
Has there been some change in Opera, or what would account for this new behavior?
-
leocg
-
raywood1 last edited by
I found a solution. This response summarizes the advice I got:
After choosing Interface > Default (not Classic) style, the “New” button at the very top of the screen still produces a new post in the block editor. That’s the button I’ve always used. I hardly even noticed the “Add Post” button. But with Default, that button does give me a choice of Block or Classic editor, and those two do deliver the different types of new post that one would expect. Apparently the Default choice is also responsible for restoring Classic Editor as an option when mousing over the title of an existing post in the list of posts. Not sure I understand the wording – Default vs. Classic – but it works.