I disabled all plugins and re-activated them one by one. The problem disappears when I disable the Classic Editor plugin. But I would prefer to keep that active for other purposes then events.

Can you help me get this sorted?

Thanks!

The site was copied to another server and the Classic editor plugin was removed without switching back the setting. (Also the domain for the new server is different.)

Now the site was stuck with the Classic editor

I reinstalled the plugin and switched back to the Bolck editor as the default.

But the change is ignored – I cannot access the block editor

Every time I edit layout a new custom field appears: classic-editor-remember

value :classic editor.

Even if I remove it, it comes back when I edit the page again.

What can I do?

The errors in the chrome dev console when clicking edit page, such as :
wp-json/wp/v2/taxonomies?per_page
wp-includes/js/dist/vendor/react-dom.min.js

This meant any time I went to edit a page, it loaded or partially loaded then froze and the only option was to terminate the tab to close the page. Even with healthcheck plugin disabling all plugins, attempting to edit with all disabled, the same issue arose. The only way I could edit pages was by disabling all plugins manually, edit, then reactivate them.

SOLUTION Installed classic editor plugin and now can edit via classic rather than block.

I dont understand why as I dont code but maybe someone knows the answer why errors were thrown or if someone has the same issue then this is a solution that worked for me.

Problem: There is a display callback passed as the third argument of WP function add_meta_box(). The sole argument passed to that callback, I call it class method ‘function html( $post ) {…}’, is a post value. Value $post is always an instance of WP_Post, as desired. If I DO NOT have the Classic Editor plugin, version 1.5, active, the block editor is active and the value of $post->ID is an int, e.g. int(11), as desired. If Classic Editor plugin 1.5 is active, the value of $post->ID is a string, e.g. string “11”. I used echo and var_dump to demonstrate that at the start of method html().

Evaluation Effort: The Classic Editor plugin 1.5 implementation is one php file and one very small JS file. I could not find anything wrong by visual inspection of those files and the core WP files (not all of them, of course). I can’t locate the plumbing that feeds the meta box display callback, e.g. my method html().

Concerns:
(1) I think that post ids should always be ints in the PHP world. True? I see core code that casts to (int). I I am supposing I should just cast to int in my callback method. In core code, wouldn’t it make more sense to use assert( is_int($post_id), … ) for post IDs that should not be unscrubbed user data from the client side but ‘inside’. Detect the problem early and trace less?

(2) The other approach would be to accept post ID regardless of its type and adapt to it. Meaning I could pass it as is to WP functions. I also need to compare post IDs from my metadata apples to apples (or start using loosing typing, which I don’t like to do).

(3) An aside, it seems (saw somewhere in WP core) that the value int(0) is NOT a valid post ID for an actual post (it’s falsy and tested that way, not my favorite semantic approach). Is it true that int zero is definitively understood to be no actual post? If so, is it documented? Importantly to me as an implementation detail, can zero be used as a post ID in the MySQL/MariaDB database (i.e. table wp_posts, column ID and table wp_postmeta, column post_id ). In my database they are the type bigint(20) unsigned. Maybe the auto_increment attribute prevents zero from being used?

I consider PHP zero to be a falsy and loose-typing hazard to avoid. I’m not a seasoned programmer, and I don’t presume what others should do.

Thanks for reading, kind person.

I am using WP 5.1.1 w/ the Twenty Nineteen theme.

I installed the Classic Editor Plugin and it appeared to work. But I couldn’t change back to the Block Editor.

I posted a query in the Fixing WP Forum and followed the suggestions offered.

– I have repeatedly cleared the cache.
– In the Profile, I checked that Visual Editor is enabled
– I have Deactivated/Activated/Deactivated the Plugin. Currently is Deactivated.
– The browser console shows No errors.

No matter what I do, The Classic Editor is still running in one Blog Post.

Please help!

Dr. T

I’m testing my site in WP 5.1 in a staging environment with the Classic Editor plugin enabled (don’t want Gutenberg yet).

I have seen posts saying that Classic Editor has all the editing options and functions of WP Edit, Tiny and all other editing plugins out there, and so those plugins are no longer needed.

That’s not true.

When I have WP Edit enabled – I can see all its editing functions in the CLssic Editor. However the moment I deactivate WP Edit – my Classic Editor’s editing options are cut by more than half – they don’t even include the font type and size!

Why isn’t Classic Editor displaying ALL the editing functions as it’s supposed to?
there is not even the font type or size option visible which indicates a serious issue – unless those additional options are somewhere hidden. Unlike WP Edit however, the Classic Editor settings don’t have any such options to be selected.

I have both WP Edit and Tiny MCE plugins, but they should not be required for the FULL and COMPREHENSIVE editing funtionality of Classic Editor.

This is really important, as I will not update my live website from WP 4.9.9 to 5.1 until this issue is resolved.

I would appreciate your advice.

thanks