Greyd.Suite Documentation
Greyd.Suite Documentation
Browse by:
Topic
Product
Feature
Greyd.Suite Documentation
How can we help ✌?
Browse by:
Topic
Product
Feature
The Turnstile block in Greyd Forms integrates a Cloudflare Turnstile check into the frontend of your form to help prevent spam submissions. Before using the block, the Cloudflare Turnstile site key and secret key must be added under Forms → Settings. If no site key is defined, a warning message will appear in the editor […]
The Aria Attributes feature allows you to enhance accessibility by adding specific aria attributes to any block in the editor. This applies not only to Greyd Blocks, but also WordPress Core blocks and any third-party blocks. Before using it, the feature must be activated on the Features page. Once enabled, each block will display a […]
GC_Post is the abstraction the Global Content plugin uses while processing posts. It wraps a WordPress post and normalizes both native WP_Post fields and Global Content–specific attributes used during synchronization and distribution. You construct it with a WP_Post, an object, or a post ID. The constructor validates input, prevents operating on trashed or missing posts, […]
The GC_Helper class acts as the nerve centre of the Greyd Global Content plugin. It groups a wide range of static utilities that support distribution, synchronisation and retrieval of posts across a multisite network and remote connections. Unlike most classes in the system, GC_Helper maintains no state; you call its methods directly without creating an […]
The Greyd Global Content plugin supports constants that allow you to change its behavior without editing the plugin code. These constants can be defined in wp-config.php or a theme’s functions.php file and must be set before the plugin loads. They are used to control SEO-related URL handling and optimize performance during content distribution. USE_CANONICAL_URL_AS_PERMALINK This […]
The Greyd Global Content plugin integrates deeply with WordPress through a series of filter hooks. Filters allow you to intercept data, change it and pass it back to the plugin at strategic points in the workflow. By hooking into these filters you can customise how the plugin retrieves global posts, builds global IDs, manages distribution, […]
The following examples demonstrate how you might hook into these filters in your own plugin. Each example assumes that the Greyd Global Content plugin is active. For a full list of available filters, see the Global Content Filters documentation. Add a Custom Property to the Global Post Object PHPCopy// Add a custom field to every […]
The Trigger feature in the Greyd Plugin allows Trigger Events to be manually triggered. See the Trigger Filters documentation for more details about the PHP filters. Use the following method to manually trigger a trigger event via JavaScript: JavaScriptCopy/** * Trigger a custom greyd-trigger Event. * * Function renamed from 'greyd_trigger.trigger()' to 'greyd.trigger.trigger()' * so […]
Here are two examples of how you can use the Greyd Form Actions. Excecute code before saving an entry PHPCopyfunction greyd_forms_action_before_entry_example( $form_data, $form_id ) { $form = get_post( $form_id ); if ( $form && $form->post_name === 'my-contact-form' ) { $option_value = get_option( 'my_custom_option' ); do_action( 'greyd_forms_log', $option_value, 'Custom option value' ); if ( $option_value === […]
This page provides code snippets demonstrating how to use action and filter hooks in Greyd.Suite. The examples complement the hook reference and illustrate practical ways to extend or adapt functionality beyond what is described in the user-facing documentation.