David Smith

Hi there

Sorry I should have explained that. There’s a great guide on how to test a PR here

Testing a Gutenberg Pull Request (PR)

I hope that helps.

I looked into this some more. I was able to get the style attribute to appear within the editor but when published it is removed on the front end of the site.

After some debugging I believe this is due to overzealous block validation marking changes to style attributes as making the block invalid. This causes the block to be serialized to the database without the style attribute.

Indeed I checked the post in the database and no style attribute was there despite my having seen it in the editor prior to saving.

There is a PR open for this very scenario. I applied it and it appears to fix the problem. I left a comment there to see if folks think the problem you raise is related.

Could you try testing out the PR and see if it works for you then?

Many thanks

Hi @mikastupnik

Please could you re-post this on the WooCommerce support forums?

Many thanks

Hi @tahireu

Please can you try installing the latest version of Gutenberg.

This is not a known issue and the Plugin is working well so I hope this will resolve it.

Many thanks

Closing this as resolved. Thanks @plantprogrammer.

Hi @mahail12

I recommend you reach out to Divi support directly as this is an issue with their product.

Many thanks

Hi @imha435

I can’t speak for your site specifically, but in general the Gutenberg Plugin has a performance test suite which runs against a post which has thousands of blocks included. If a threshold is reached then the team are alerted.

Some things to check might be the size of your images. Very large images may have an effect. You could try resizing the images and see if that helps.

Alternatively you could remove the content and re-add it gradually until you find the set of blocks causing the problem.

If you can find a reduced test case we’ll be happy to take a look.

Look forward to hearing back.

Hi @wordpresslover7

Sorry to hear your frustrated with the editor.

The docs you’ve referenced are for the classic editor. The block editor keyboard shortcut docs are here.

When I’m using the editor I create headings using the markdown shortcut syntax. To do that simply add a new line (hit ENTER) and then type # and then SPACE. That will add a <H1> but if you add more characters you will get different levels of heading (e.g. ### will create a h3).

I hope that helps?

The editor is different but I hope you will be able to give it another try. If there are features missing please do feel free to raise an Issue on Github.

Thanks @timfransen. Glad you managed to find the right place to post.

Hi @locksoft

I am aware of several efforts in this area around block validation and HTML.

I’m hopeful you will see an improvement in this area in the (relatively) near future.

I’ll close this one out for now but please do keep an eye on the Issue.

All the best

Hi @dixravi

I’m going to close this one out as there’s been no response.

I hope you managed to find a solution to your issue.

All the best

As this error has been fixed in the latest version of the Plugin I’m going to close this one out.

Thanks for your question.

@sdwire I hope you don’t mind but I’m going to close this one out as it looks like the question has been answered.

Many thanks

Hi @evemassacre

Let me try to help here.

When you active the setup you’ve described you won’t see an “FSE” menu item as that is an umbrella term and not used within the WordPress interface.

Rather will see Edit underneath Appearance. I’d definitely recommend taking this course from the official WordPress learning resources on how to use the Site Editor. It should make things a lot easier for you.

I hope that helps?

Hi @sybakhar

Thanks for letting us know.

I’ll close this one out.