Birgit Pauli-Haack

Hi Kevin,

This is an interesting problem (for me, I like puzzles) – I feel for you that this is disconcerting and disruptive of your work…

Are you able to see any javascript errors in the browser console, when you try to save your post?

There might be a problem with permissions for the REST API, now that you moved the site and backend and frontend are not in the same directory.
Now this is just a hunch on my side. Can’t say for sure until we have additional information.

As it’s been a few days since your reported it here. Since then a new Gutenberg version was release on Nov 15, 2018 with a considerable amount of fixes. Could please test this again with the new version and let us know if anything has changed. There might not be any changes, and this quirk persists.

A good next step would be if you could find out the javascript error via the browser console and maybe you can turn on Debug so see if there are server error messages as well.

• This reply was modified 7 years, 5 months ago by Birgit Pauli-Haack.

HI there,
Thank you for bringing this up! Good news, I think….
This has been fixed in 4.4.. Would you mind give it another whirl and report back?

Thanks in advance!

Hi there,

At this stage of Gutenberg doesn’t have ‘page’ building capabilities outside the space of a post or a page. And there is no ‘section’ block (yet)

You might need to experiment a bit with various blocks that allow for left / right alignment (float).
There is a beautiful “media + text” block available and a column block in the default list of blocks. And there are quite a few plugins in the WordPress repository that push the envelope of the editor to assist with various layouts.
To name a few: Otter Blocks, Atomic Blocks, Stackable, Advanced Gutenberg and Editor blocks. I found useful blocks in all of them. And we use them in production for some of our sites.

Disclaimer: As Gutenberg is still under active development not every plugin works with latest Gutenberg plugin version.

Let me know how it goes!

• This reply was modified 7 years, 5 months ago by Birgit Pauli-Haack.

The Gutenberg gallery block doesn’t have a random on/off switch. The images are loaded in the order they were added to the gallery. If you want to change the order, click on the little pencil icon in the block toolbar. That opens the Media Gallery view, and you can via drag and drop change the order in which the images appear. If you use multiple columns it goes left ot right per row and then creates a new row. In other words when you have six pictures in three rows images 1,2,3 are in the top row and images 4,5,and six are in the second row.

Hope this helps

Who know what happens after two or three years? And why worry now?

Why would people abandon WordPress? That depends who the user is.
If it’s a business the switching cost to a complete different CMS need to be weighed against the cost to install the Classic Editor and keep doing what one is doing. – not leaving

A developer actively working with clients, also needs to weigh his feelings against what’s good for his clients, and what will cost the least amount of disruption – probably not leaving

If the user is a consultant, again weighing the switching costs for himself, his team and his customers against, the effort it cost to install Classic Editor.

If the user is a developer associated with WordPress in her spare time, she might think that a different CMS would make it more fun. That might also be offset by developers who think WordPress has gotten cool(er) again with Gutenberg being based on a modern, JavaScript framework, and they find a new home in the WordPress Community. – maybe / not sure what the net-loss would be.

If the user is a blogger, she will after the initial learning curve embrace Gutenberg as it make life so much easier with reusable block, she can loose a bunch of plugins that provided missing features now built into Gutenberg. There is lots to like for a content creator.

The conclusion that Classic Editor plugin won’t work after a while, assumes that the WordPress dev team won’t maintain the classic Editor in the future. That does not seem to be the case: Matt Mullenweg stated that it will be available years to come. And the WordPress dev team made a commitment a long time ago not to abandon users.

Sure. – nothing last forever, nothing is ever perfect, and nothing is ever finished. – the Wabi-Sabi of web development and life

Your English fine. Don’t worry about that.
Yes, the title tag is to be set for each image individually. I wasn’t very precise. When I wrote globally, I meant ‘not changed for single posts’, that’s probably why it’s not in the sidebar of Gutenberg, Those settings are mostly for Post-Level properties.

The options panel comes into play on upload of the image an belongs to the Media library. It seems it doesn’t allow you to edit when you add an image to the image block via Media Library, that’s where the title is set globally. Interestingly enough, that panel is not offered when you upload an image. You would need to edit through the Media library. It’s definitely only a work around. Certainly not ideal. I added the ‘missing title’ attribute to the Block audit issue for the image block on GitHub