Certain functions (e.g. trigger events for accordions) require scripts.However, some cookie tools (e.g. Cookiebot) automatically block all kind of scripts - no matter if they do set a cookie or not - when not set otherwise. In that case it may happen, that the default.js script of GREYD.SUITE - which is necessary for triggers to work properly - is also blocked.To prevent that from happening, just exclude relevant files & scripts in your Cookiebot settings.

Greyd.Suite offers you an Import/Export option for any post with which you can easily export and import posts including its translations. When exporting single posts, you’ll be asked whether you want to include translations or not.However, in some cases there might be problems:Bulk Exports: Unfortunately the native WP bulk export does not work with translations. If you want to export several posts including their translations, please use the option “bulk export with translations”.When importing multilingual posts to another website, only those language versions will be imported, that are set up on that website.If no languages are set up at all on the target website, all post versions will be imported without language information, so you might get the same post twice on the target site (e.g. the German AND English version)

Greyd.Suite Documentation

Compatibility with other plugins

Greyd.Suite works alongside many third-party WordPress plugins. In practice, most popular tools run smoothly. However, overlapping features can lead to visual inconsistencies or minor conflicts, especially around block styling in both the editor and the front end. Conflicts are more likely when two plugins offer the same feature areas such as animations, custom post types, or block design controls. When external blocks are used inside Dynamic Templates or Popups, styles may occasionally not load correctly or individual custom blocks may fail to render. Non‑block plugins typically coexist well, as they operate in separate domains.

Integrations

WPML & Polylang

Greyd.Suite has deep integration with WPML and Polylang to support multilingual workflows. This includes:

Automatic inclusion of translations when exporting a full post type via Global Content.
Language-specific configuration for all default post types in Greyd.Suite.
Extended translation support for Dynamic Templates, ensuring all template parts can be localized.
URL handling inside Greyd functions is filtered through WPML and Polylang’s own functions, preserving language-specific paths.
Special compatibility logic inside Greyd.Forms to resolve multi-domain mapping issues when using wp-ajax.
General use of WPML/Polylang functions throughout the codebase to maintain language context in frontend and backend outputs.

For more information, see the article All you need to know about multilingual FSE websites.

WooCommerce

Greyd.Suite supports WooCommerce and WooCommerce Germanized. You can edit all WooCommerce templates and blocks in the Site Editor. Greyd features like advanced queries, dynamic tags, conditional content, popovers, custom filters, and Global Content work with the product post type. With Site Connector, you can sync products across multiple sites.

Advanced Custom Fields (ACF)

ACF integrates cleanly with Greyd.Suite. You can use ACF fields in dynamic tags and queries. Both plugins run in parallel without conflicts. Post type and taxonomy registrations are not shared, so structures created in one plugin are not editable in the other. See the ACF Integration documentation for more details.

Yoast SEO & Rank Math

Greyd.Suite provides SEO extensions for Yoast and Rank Math. These add integrations for metadata, dynamic tags for SEO fields, conditional outputs, and improved structured data handling. See the SEO Extensions documentation for more details.

Tested plugins & results

ACF: Fully compatible in parallel. Duplicate post types are prevented with clear warnings. Cross‑editing post types or taxonomies between ACF and Greyd is not supported.
CoBlocks: Useful ready‑made blocks. In Dynamic Templates and Popups, styles sometimes fail to load; some blocks (e.g., Hero) can throw editor errors in templates.
Croco Blocks (JetGridBuilder & JetStyleManager): JetGridBuilder is useful for quick post layouts but its custom blocks do not work inside Dynamic Templates. JetStyleManager affects only Croco blocks and otherwise has no impact.
Editor Plus: Overlapping features with Greyd. Some styling issues (checkbox styles, hotspot jumps, button hovers) and a case where a dynamic URL on core/button is not passed to the front end.
Extendable: Styling issues with buttons, hotspots, and forms. Editor shows minor glitches (e.g., dynamic image focus outline) while front‑end generally follows theme styles.
Generate Blocks: Minimal additional value next to Greyd. Minor inconsistencies in templates and forms; otherwise functional.
Gravity Forms: Fully compatible when used alongside Greyd Forms as a separate system. Embedding a complete Gravity Form inside a Greyd form renders but will not submit; use each form type independently.
Kadence: Not a block theme and duplicates many Greyd features. Multiple style issues (buttons, hotspots, forms). Usable, but not recommended in combination.
Meta Box: Works in parallel if post type slugs differ. Using identical slugs causes one plugin to overwrite the other’s registration; avoid duplicate slugs.
Stackable: Free version works, but there is significant feature overlap with Greyd. Minor editor styling quirks; combined use is usually unnecessary.

Was this article helpful?

Thanks for your feedback!

FAQ

Why do some triggers not work when cookies are blocked?

The export with multilingual post versions does not work.

Last updated:

August 29, 2025