[Support request] Elements editor content width issue in WP 6.0

[Gary]

I’m experiencing an issue in Elements again where the editor width is not respecting the value set in block element width setting with WP 6.0.

I’m running the latest versions of GP 3.1.3 and GPP 2.1.2 which I think this was supposed to be fixed in looking at older posts with similar width issues with block elements editor width. I’ve even tried having this snippet active again to fix it from an older post from Tom posting a temp fix:

https://generatepress.com/forums/topic/block-editor-width/

Just wondering if there’s issues with the block element width again following WP 6.0 update ? Or if there’s a newer fix for this issue?

If it helps I’m trying to get this working in a site footer element, but the editor seems contained to 840px width whatever I do.

Thanks

[Fernando]

Hi Gary,

I’m on WordPress 6.0 with the same updated GP versions, and I’m not experiencing the same issue.

If you try #1 here, does the issue still exist?: https://docs.generatepress.com/article/debugging-tips/

It would be good to take a backup of your site before doing so.

Kindly let us know how it goes.

[Gary]

Hi Fernando

Thanks for the reply, I can confirm disabling all non GP/GB related plugins has no effect and the editor width issue still remains.

As this is a staging site I am running the latest beta versions of GB and GB Pro. I’m now wondering if this could be the issue combined with WP 6.0?

Thanks

[Gary]

Hi Fernando

Just to let you know I’ve tested this with two other sites, one also using GB / GB Pro betas and one using latest stable production versions. In the former I get the same issue with block elements not spanning full width and the editor width setting having no effect. With the latter using the current production versions of GB/GBP, block elements span full width as expected and the editor width control works.

Therefore I’ve raised this as an issue on GP github here:

https://github.com/tomusborne/generatepress/issues/391

Thanks

[Ying]

Hi Gary,

Thanks for reporting this to us.

Tom has replied in your opened issue: “This should be temporarily fixed in the latest GB 1.5 and will be permanently fixed in GP 3.2/GPP 2.2.”

[Author]

Posts