Blocksify settings control CSS delivery, the Design Library button, AI access, service keys, rollback, and uninstall cleanup.
Use this reference to understand each setting, its default, and the maintenance actions.
Where to find it
- Go to Blocksify → Dashboard → Settings. The Performance panel opens.
- Select the panel that contains the option you want to change.
- Change the option, then click Save changes. A Settings saved. notice confirms the update.
The save bar shows Unsaved changes until you save. Reset to defaults resets every dashboard setting after confirmation, not only the visible panel.
Performance
The Performance panel controls how Blocksify delivers generated CSS. Its Cache subsection provides the Clear cache button.
| Setting | Description |
|---|---|
| CSS output mode | External file (recommended), the default, writes one cached CSS file per page in uploads for browser caching. Inline in head prints the page CSS in its head instead. See how Blocksify keeps your site fast for the wider delivery model. |
| Clear cache | Clears Blocksify’s per-page CSS files and the Design Library‘s cached item list. CSS is rebuilt on the next page visit, and the library downloads its list again when opened. |
Clear cache reports how many entries were removed. It does not change the selected CSS mode.
Editor Enhancements
The Editor Enhancements panel chooses where the Design Library launcher appears in the WordPress editor.
| Setting | Description |
|---|---|
| Design Library button | Document toolbar (top-left) is the default. Choose Blocksify settings sidebar to move the launcher into that sidebar, or Hide to remove it from the editor. |
Save, then reload the editor before checking the new position. Hiding the launcher does not delete inserted patterns.
AI
The AI panel contains the Blocksify AI access card, application-password action, copyable endpoints and commands, and one optional exposure setting.
| Setting | Description |
|---|---|
| Offer these abilities to MCP clients | Off by default. Turn it on only when another active plugin provides an MCP server and should list Blocksify abilities to its clients. Direct access through the WordPress Abilities API works whether this setting is on or off. |
The card also shows Endpoints, Authentication, Call an ability, and Show published abilities. Create an application password makes a credential for the current WordPress account; follow Connect an AI assistant to Blocksify for the complete flow.
Note: Blocksify does not include an MCP server. If no server-providing plugin is active, turning on the exposure setting does not create a new connection.
Integration
The Integration panel groups credentials for reCAPTCHA spam protection and Mailchimp subscriptions used by matching form fields and submit actions.
| Setting | Description |
|---|---|
| reCAPTCHA version | v2 — “I’m not a robot” checkbox is the default and shows a checkbox field. v3 — invisible (score-based) scores visitors without a checkbox and needs its own v3 key pair. |
| reCAPTCHA site key | The public key for the selected version. After entering it, click Connect to check that its format looks valid. |
| reCAPTCHA secret key | The private verification key. It is checked on the server and is not exposed publicly; click Connect to validate it. |
| reCAPTCHA v3 score threshold | Used only with v3. The accepted range is 0.0–1.0, in 0.1 steps; the default is 0.5. |
| Mailchimp API key | Used by the Mailchimp submit action and normally ends with a data-center suffix such as “-us18.” Click Connect to validate it. |
A successful Connect check does not save the value. Click Save changes after checking the keys; saved secret values return to the screen masked.
Version control
The Version control panel can reinstall an earlier stable Blocksify release and decide whether plugin deletion also removes user-authored Blocksify data.
| Setting | Description |
|---|---|
| Delete all data on uninstall | Off by default. Turn it on to delete saved forms, Style Classes, and templates when Blocksify is deleted. Leave it off to preserve that content for reinstalling or troubleshooting. |
Roll back to a previous version
Roll back to a previous version lists earlier stable releases from WordPress.org. Choose an earlier version from the dropdown, click Roll back, and confirm; WordPress reinstalls that release inside wp-admin and reports the result.
Warning: Rolling back replaces the current Blocksify plugin files with an older release. Keep the browser tab open, then check the dashboard and important pages after the process finishes.
If the host needs filesystem credentials, Blocksify offers Continue on the WordPress update screen. After a successful inline rollback, click Reload dashboard to load the installed version.