Blocks
- The default gap between columns sometimes leads to the bootstrap grid unexpectedly breaking into multiple rows. An easy solution is to set the gap to zero in the sidebar settings tab. We are working on a better solution.
- The content block displays the message “Block cannot be used in itself” when used inside a query loop outside of the Site Editor. This is a known core issue and does not affect the front-end.
- Blocks with interactivity in the front-end, like the form block, search blocks, the hotspot block or the popover block often appear to be crashed on loading the editor. This happens when you switch between languages in multilingual websites. The reason is that default text, like “please select”, is saved in the post content. An easy solution is to use the Greyd Editor Helper (top right “eye”-icon) and fix all blocks with a click of a button. We are working on a better solution.
- The new Query Loop features available in the Gutenberg Plugin, like the option “force new pageload”, are not yet supported.
- New Sticky, Fixed & Pinned Box:
- The preview is not working properly in the Block Editor.
- New Popover Block:
- The preview of the popover, offcanvas and overlay menus doesn’t always work correctly with the Classic version.
Compatibility
- Updating the Hub from old versions can lead to a fatal error, “
Cannot redeclare is_greyd_blocks()”. Try updating the classic theme first. - The Full Site Editing version of Greyd.Suite is generally not compatible with Wordpress 5.8 and lower.
Global Styles
- Tables and notices cannot be globally designed yet, in the same way as they were in the Classic version.
- Note: The grid works differently now – it was adjusted to be closer WordPress Core behavior. We recommend watching the tutorial.
Patterns & Templates
- More content patterns and example will be added very soon. Stay tuned!
- All templates inside the Template Library have been designed for the classic suite. If you install a Full Site Template on a pure FSE install, this can lead to a white screen in the frontend. You will need to go to the backend manually and switch the theme. It is best to run the Classic to FSE Converter afterwards.
WooCommerce
- The theme has not yet been extended for WooCommerce.
Converter Classic to FSE
- The header and menus are only converted into a basic block layout. You still need to rebuild the header manually for now.
- Converting theme styles from a child theme is not supported yet. Please switch to the default theme first, import your styles using the Hub, and then switch to the FSE version. This way you can properly convert your Customizer Styles into Global Styles.
- Almost all colors will be displayed properly but they are sometimes not selected in the editor. The slugs of the colors changed, so when editing those colors, you need to reselect them. The definition of those colors is still dynamic.
- After transforming your site you might still experience some layout issues, which you will need to amend manually.
- Font sizes might differ after transforming your site.
- Negative margins are usually not displayed correctly, because WordPress core blocks do not fully support them yet.