Home / Plugin: GenerateBlocks / Compatibility with block themes
Is there a roadmap to enhance compatibility with block-based themes? In the theme editor, the breakpoint functionality doesn’t visually work; it’s not linked to the responsive views of the native editor. It would be great to standardize that. Thanks for your awesome work!
Hi there,
any particular theme?
And does the issue occur of you use the Responsive view options in the GB Block Settings sidebar ( not the ones in the top bar ) ?
Hi David !
I’m working on a custom theme based on blocks, more precisely, I’m making a custom archive page.
But I’ve also tested it with the Twenty Twenty-four theme and the plugin’s behavior is the same: The responsive setting buttons for Generateblocks blocks (the ones in the block setting sidebar, not the ones at the top right of the editor) don’t act on the interface display in the editor like they do if you are setting up a Generateblock block when editing a page or a post, for example.
However, it would be interesting to synchronize the display of the Generateblock responsive interface with the editor’s native responsive display (top right buttons).
I’m not sure if I’m making myself perfectly clear, tell me what you think?
In Dashboard > GenerateBlocks -> Settings, can you check that the Sync Responsive Previews is checked ?
Yep, it is 😁
I have no issue switching between responsive views on a Twenty twenty four theme site, so it’s likely caused by something in your site’s specific enviroment.
Screenshot for your reference: https://app.screencast.com/agAHNKa5OnkD7
Can you disable all other plugins and custom functions, switch to Twenty twenty four theme and check? Let me know 🙂
I haven’t yet tested with all plugins deactivated, but I’ll keep you posted. However, I did notice these errors in console, so maybe that gives you some clues:
global-styles-css-custom-properties-inline-css was added to the iframe incorrectly. Please use block.json or enqueue_block_assets to add styles to the iframe.generateblocks-css was added to the iframe incorrectly. Please use block.json or enqueue_block_assets to add styles to the iframe.global-styles-css-custom-properties-inline-css was added to the iframe incorrectly. Please use block.json or enqueue_block_assets to add styles to the iframe.generateblocks-css was added to the iframe incorrectly. Please use block.json or enqueue_block_assets to add styles to the iframe.global-styles-css-custom-properties-inline-css was added to the iframe incorrectly. Please use block.json or enqueue_block_assets to add styles to the iframe.generateblocks-css was added to the iframe incorrectly. Please use block.json or enqueue_block_assets to add styles to the iframe.I use firefox, I’ll test to see if the problem is the same on a Chromium browser.
The problem may also come from the Headers Security Advanced & HSTS WP extension, but if the styles are loaded “locally” it shouldn’t be a problem.
Hi there,
those console logs are simply notices, some of which are related to core files. That would not be related to the issue you’re seeing. Let us know what you find
Hello, just to keep you informed, everything is now working normally since update 1.9, thank you!
Quentin Le Duff.
Glad to hear that!
