This document outlines the current known issues in Greyd.Suite and provides practical interim solutions where available.
Blocks
- In the Block Editor, the default gap setting between columns can cause the Bootstrap grid to unexpectedly wrap into multiple rows in the editor. To avoid this, set the gap to zero in the sidebar settings tab. A more robust fix is in development.
- When using the content block within a query loop outside the Site Editor, the block may display an error message “Block cannot be used in itself.” This stems from a core WordPress limitation and does not impact the frontend display.
- Interactive blocks such as Form, Search, Hotspot, or Popover may appear broken when loading the editor following a language switch in multilingual setups. This occurs because default placeholder texts like “please select” are stored in post content. A quick workaround is to use the Greyd Editor Helper (eye icon in the top right) to resolve all affected blocks in one click. A more elegant solution is being developed.
- New Query Loop features introduced in the Gutenberg Plugin — such as the “force new pageload” option — are not yet supported in Greyd.Suite.
- The new Sticky, Fixed & Pinned Box block does not display correctly in preview mode within the Block Editor, and the Popover block’s previews for off-canvas or overlay menus may fail to render properly in the Classic version.
Compatibility
Upgrading Greyd.Hub from older versions can trigger a fatal PHP error: Cannot redeclare is_greyd_blocks(). To avoid this, update the Classic Suite theme before updating the Hub.
Greyd.Suite’s Full Site Editing (FSE) version is not compatible with WordPress version 5.8 or lower.
Global Styles
Global styling for table elements and notice boxes is not yet available in the FSE version, unlike in the Classic version. The grid system has been updated to better align with WordPress Core; users are encouraged to follow the available tutorial for guidance.
Patterns & Templates
The Template Library currently includes patterns that were designed for the Classic Suite. Applying them in a pure FSE environment may result in a blank frontend (white screen). In such cases, switch back to the backend and select a compatible theme, or initiate the Classic-to-FSE converter afterward.
Classic-to-FSE Converter
The converter currently generates only a basic layout for headers and menus. You will need to rebuild the header manually post-conversion. Converting styles directly from child themes is not supported yet; the recommended workflow is to switch to the default theme first, import styles via the Hub, and then activate the FSE version to ensure proper conversion of Customizer styles into Global Styles.
Some layout issues may persist after conversion, including differences in font sizing, incorrect rendering of negative margins (due to limited core block support), and missing color selections in the editor due to changed slugs. In such cases, reselect theme settings or reapply color definitions manually.
Classic Greyd.Suite Theme
If you’re still using the Classic Greyd.Suite Theme and experience that the design looks broken and CSS is not loading properly, there might be issues with CURL occuring on this site. What you can do is comment out some lines 222 – 248 in the file greyd_suite/inc/vc/helper.php.