The plugin has two settings pages in the WordPress admin under the top-level Page Blocks menu (moved there in 2.1.0).
Page Blocks settings moved with the 2.1.0 menu restructure: everything now lives under the top-level Page Blocks menu rather than WordPress’s Settings. This lesson tours each setting, including the three frontend CSS toggles added in the 2.2 and 2.3 releases: semantic reset, typography, and utility classes.
Page Blocks Builder Settings
Location: Page Blocks > Settings
This page controls which post types the visual builder is available on.
Enabled Post Types
A checklist of all public post types on your site. Check the ones where you want the Page Block Gutenberg block and the frontend visual builder to be available. By default, Posts and Pages are enabled.
When a post type is enabled.
- The Page Block appears in the Gutenberg block inserter for that post type.
- The “Page Blocks Builder” link appears in the admin bar when viewing a singular post of that type.
- The visual builder grants access for posts of that type.
When a post type is not enabled.
- You can still use the Page Block in the Gutenberg editor (the block is registered globally), but the visual builder won’t be accessible from the admin bar.
- Direct builder URL access will be denied for posts of that type.
The setting is stored in the gt_pb_builder_post_types option. It can also be overridden programmatically via the md_page_blocks_builder_post_types filter (see the Hooks and Filters chapter).
Preview Injection Filter
The settings page includes documentation for the md_page_blocks_builder_preview_injection filter. This section is informational only. It shows an example of how to use the filter to inject custom HTML, CSS, or JavaScript into the builder’s preview iframe. See the Hooks and Filters chapter for full details.
Page Blocks License
Location: Page Blocks > License
This page manages your plugin license for automatic updates.
License States
Inactive. No license key has been entered. You’ll see a text field to enter your key and an “Activate License” button. A link to purchase a license is shown below.
Active. Your license is valid. The page shows a masked version of your key (first 4 and last 4 characters visible, the rest replaced with asterisks) and a “Deactivate License” button. If your license has an expiration date, it’s shown. Lifetime licenses are labeled as such.
Expired. Your license has expired. The page shows a warning with the expiration date, a “Renew License” button linking to the purchase page, and a field to enter a new license key if you’ve already renewed.
License Verification
The plugin verifies your license in two ways.
On activation. When you enter a key and click Activate, the plugin contacts the license server to validate the key, register the activation for your site URL, and store the activation hash.
Weekly cron check. A scheduled WordPress cron event runs once per week to verify the license is still valid with the remote server. If the license has been revoked or expired, the local status is updated accordingly.
Automatic Updates
When a valid license is active, the plugin hooks into WordPress’s plugin update system. It checks the license server for new versions every 12 hours (cached via a transient). When an update is available, it appears on the standard WordPress Plugins > Updates page and can be installed with one click.
Admin Notices
When you’re on a post editing screen or the plugin settings page without a valid license, you’ll see a dismissible notice.
- Inactive license: An info notice suggesting you activate your license.
- Expired license: A warning notice suggesting you renew.
These notices don’t appear on the license page itself to avoid redundancy.
Quick answers to common questions:
What do the three frontend CSS toggles do?
Semantic Reset is a ~1KB modern reset; Typography adds system-font defaults with clamp()-scaled headings and proper measure; Utility Classes provides ~330 Tailwind-inspired utilities where the frontend inlines only the rules each page actually uses. All three are independent and off by default.
Which post types can use the builder?
Whatever the post-types setting allows, pages by default, filterable in code via md_page_blocks_builder_post_types. The settings page exposes the same control without code.