herbie888

@azaozz “Try Gutenberg” panel showed up in same context as described by @davemac, seems to be fixed with Classic Editor 1.3, thanks for fast response.

@azaozz When updating a few WordPress 4.9.8 sites from 0.5 to 1.2 today, the “Try Gutenberg” panel re-appeared in WordPress dashboard. It was hidden before and should stay hidden. Is that a known issue?

The block editor has been developed since 1.5 years.

Now it has been released to regular users as mandatory replacement for classic editor.

Regular users expect that now available blocks at least match the existing features of classic editor.

As obviously features are missing and no block library exists yet, they will ask questions like this thread, again and again, and expect answers which do not include developing variants or waiting for future phases or how interesting things might be.

Their future is now. They want to get their work done with the editor now. @vesaraiskila wants to indent the paragraph now. The only simple workaround is via “Classic” block, as explained above. That’s it.

Regular users won’t create block variants.

They look for features they had for years, like single/double/triple/.. indentation with a click.

And they will wonder why their existing indentations get lost when converting old content to blocks.

If the solution is as simple as you describe, I am wondering why this is not in core already, it’s a backwards compatibility issue after all, similar to this issue, @vesaraiskila and others would be happy.

@astral4ik Maybe this similar/same question here helps.

Click “Increase indent” button in “Classic” block automatically uses a fixed indent of style="padding-left: 30px;" consistent in any post.

That’s the way indenting whole paragraphs is done in WordPress since many years.

Adding own CSS and an own class is way too complex for regular users.

Link to Classic Editor had a bug which appears to have been resolved with Classic Editor 1.2.

@vesaraiskila

• use a “Formatting > Classic” block
• if not visible yet, open second toolbar line (rightmost icon)
• enter and select your parargraph(s)
• click “Increase indent” button

Default for “Allow users to switch editors” seems to work as expected now with Classic Editor 1.2.

The message “The Classic Editor plugin prevents use of the new Block Editor. …” in “About WordPress“ still shows regardless off any setting.

@azaozz Would suggest to fix this logic bug very soon, so finally the plugin really works as expected and as promised.

People are getting really upset in various forums, chats and social media platforms, wild conspiracy theories about behind-the-scenes influence of Automattic and money coming up and being discussed. Further delays and/or other features or notices which still point to Block editor after installing this plugin won’t really help here, all this gives the voluntary supporters and developers already a bad name now. ??

@azaozz seems @arhit actually had 5.1.something which does produce that error, see also here:

If you use the WordPress Beta Testing plugin and have the option set to download Bleeding Edge, DON’T UPDATE! It will put your site on the 5.1 Alpha branch which does not have Gutenberg. …

Source: https://twitter.com/jeffr0/status/1071143326315937792

@azaozz probably @arhit meant 5.0.1-alpha-43972 which is currently available, even @matt runs it in production on his personal page.

@padraigbeirne Thanks for input, but this thread is about the “official” WordPress supported plugin, which currently does not work as promised and a few 100.000 users who as precaution had installed the older 0.5 version are not even aware yet of the malfunction = suddenly again visibility of Gutenberg for their clients, schools, ngo’s, sites which they technically support.

Besides that, would suggest to follow the coming WordPress 5.x updates in detail, where TinyMCE seems to be moved around/elsewhere/out of core/similar, so maybe the “official” WordPress supported plugin will be the only real option after a while.

It is supposed to work the best for the most users.

@azaozz It is supposed to work as expected and as @matt promised to serveral 100.000 users of the older version 0.5 of this plugin.

Users who had switched off the Gutenberg editor in previous versions of Classic Editor plugin expect to have it switched off also in current versions of the plugin.

It’s pretty simple, if “Replace the Block editor with the Classic editor” setting had been selected before, the default for the new option “Allow users to switch editors” has to be “No”.

Nothing else, no “it’s not easy”, no “I’m aware of dislike”, no “but….. ??”, in this case the default has to be “No”.

Everything else is a bug. And a betrayal against serveral 100.000 users.

If there has been no previous setting saved for “Replace the Block editor with the Classic editor” yet, do whatever you want with the default.

Same problem with Classic Editor 1.1.