markciotola

I understand your views, even if your view of blocks seems to be one big long run on paragraph.

This is not a helpful attitude.

The editor will break up your content into blocks all by itself.

A collection of blocks is much more difficult and time consuming to edit than a scroll of text.

This was really well-written and speaks for a lot of us in the WordPress community (and perhaps even most of us). This also characterizes the position in which most of our site users will feel themselves. Many of our authors don’t know HTML. They like the current WordPress because of the sensible, efficient usability of the current editor. Also, most of my users will feel really frustrated with Gutenberg’s balkanization of content alluded to in the above review.

• This reply was modified 6 years, 7 months ago by markciotola.

paragraph separation (due to them being split into blocks now)

Paragraphs being spit up into their own blocks is one of the biggest pain points for content editing in Gutenberg. For short paragraphs, all of those blocks (with their rectangles and tool bars) clutter up the entry area make editing content much more difficult.

• This reply was modified 6 years, 8 months ago by markciotola.

Is there a working group for such a fork? Why haven’t some of the power users taken a lead in forking?

> it simply gets in the way of my writing unlike the Classic Editor

Exactly! Gutenberg balkanizes content, which makes content entry and creation with Gutenberg a clumsy affair.

All of the blocks for long posts add a lot of background clutter in terms of boxes and menu icons. It really breaks up the page in editor view and makes it nearly impossible to view and edit, especially for long posts with multiple headings (and often a few levels subheadings) and lots of inserted media.

Although having a different editing tool bar for each box sound like a good idea, the problem is that our users need many if the MCE tools, even for headings and lists, and those tools are missing from many of the block menus. It is frustrating and confusing.

Also, we have customized the MCE menu, so we will have to write a custom menu for every type of block.

> the amount of time wasted clicking buttons and options in order to get anything done is just too inefficient and frustrating since it never seems to actually achieve what I’m attempting to build.

I am having the same experience. Version 3.1 doesn’t really make this any better.

WordPress needs to get more feedback from high volume content entry authors.

From a content entry view, this is a really clunky, inconsistent interface. My users enter large volumes of content. Gutenberg with its block system will really slow them down for entry, editing and review. They don’t need to design new looks for posts and pages. (In fact, we need to enforce a consistent look and feel via themes, so we don’t want our users to have lots of design flexibility).

I am going to face a major revolt by my users. Even the ones who want to keep using it will require a lot of training. The learning curve will be much higher for new users than with the existing editor.

And this doesn’t even include the cost of rewriting our extensive set of custom plug-ins.

>new interface standard will make for a much better and more consistent overall user experience

That future is far from arriving, yet we are being forced into Gutenberg now (or very soon). If is like being locked into a flying car before it has wings that is then thrown off of a cliff.

When is 4.9.1 expected to be released?

Most of my theme development is on hold until then.

Don’t risk trying to reload if you get this error. I did, and it killed my entire site. My host could not restore it from their backups. (I have my own back-ups, but I don’t want to have to keep restoring.)

I don’t even get the option of changing to a standard theme. There is just nothing. I never had a white screen problem before I couldn’t fix (and I do know some PHP).

Will 4.9.1 fix this? If so, when will that be out?

This issue killed one of my entire sites, and my host could not restore it from their back-ups. I have my own back-ups, and this was just a development site, but I need the rapid back-and-forth between the theme Editor and viewing changes.

I have read that 4.9.1 will fix this issue? When will that be out?

Most of my theme development is on hold for now. (It is just too inefficient to do all of the development by FTP). The old way things worked was GREAT for development!