Skip to content
Gaurav TiwariDocs

Installing GT Page Blocks Builder

Updated October 17, 2026

Installing GT Page Blocks Builder starts with the plugin ZIP and a WordPress administrator account. You can activate the plugin and build the course demos without an AI-provider key.

The full-page template exercises use a classic theme. The plugin also renders Page Blocks with block themes, but its two PHP page templates are not registered for those themes in version 3.0.0.

Requirements

Check the site and your account before installing.

  • WordPress 6.0 or later.
  • PHP 8.1 or later.
  • An administrator account for installation and library management.
  • Permission to edit the target page, with its post type enabled, for builder access.

Installing the Plugin

The WordPress plugin uploader accepts the plugin ZIP.

  1. Open Plugins > Add Plugin > Upload Plugin.
  2. Select the Page Blocks Builder plugin ZIP, install it and activate it.
  3. Open Page Blocks > Settings to confirm the enabled post types.
GT Page Blocks Builder active in the WordPress Plugins screen.
The Deactivate action identifies the active plugin.

A demo JSON file is page content. It belongs in the builder’s importer, not the plugin uploader.

Initial Configuration

Posts and Pages are enabled by default. Leave the AI-provider fields empty for the manual course exercises.

Page Blocks settings showing enabled post types and empty AI-provider fields.
The manual builder and JSON imports do not need an AI-provider key.

License Activation

The plugin includes a license system for receiving automatic updates. Go to Page Blocks > License, enter your license key, and click Activate License.

Once activated, the plugin checks for updates through the WordPress plugin updater. You’ll see available updates on the standard Plugins page and can update with one click, just like any other plugin.

If you don’t activate a license, the plugin still works. You just won’t receive automatic updates and will see a notice on relevant admin pages reminding you to activate.

File Structure

After installation, your plugin directory will look like this.

page-blocks-builder/
    page-blocks-builder.php        Main plugin file
    index.php                      Security index
    includes/
        class-license-manager.php  License and update management
    assets/
        js/
            block-editor.js        Gutenberg block registration and editor
            builder-shell.js       Frontend visual builder application
        css/
            block-editor.css       Gutenberg editor styling
            builder-shell.css      Visual builder styling
    templates/
        builder-shell.php          HTML shell for the visual builder
        page-blocks-builder.php    Standard page template
        page-blocks-full-builder.php  Full-page template (no header/footer)
        settings-page.php          Admin settings UI

Verifying Installation

After activating the plugin, you can verify everything is working.

  1. Open any page in the Gutenberg editor.
  2. Search for “Page Block” in the block inserter. You should see it under the “Page Blocks” category.
  3. Visit any page on the frontend while logged in. You should see a “Page Blocks Builder” link in the admin bar (under the Edit link).

Uninstalling

Deleting the plugin removes its settings, stored AI keys, related transients and scheduled events. The reusable library and its revision table are kept unless Delete data on uninstall was explicitly enabled.

Inline Page Block markup remains in post_content, but keeping the markup is not the same as keeping it rendered. The Page Blocks renderer must be available, or you must convert the content before removing the plugin.

Export the pages and back up the site before uninstalling. Do not enable deletion of the library as a cleanup step unless you intend to remove that content.

Quick answers to common questions:

What are the current requirements for Page Blocks Builder?

The plugin requires WordPress 6.0 or later and PHP 8.1 or later. Installation needs an administrator; builder access also needs permission to edit the target page and an enabled post type. The demo environment used WordPress 7.1, with the editor limitations described in Troubleshooting.

Where did the license page move?

Since 2.1.0 the plugin has its own top-level Page Blocks menu: All Page Blocks, Add New, Settings, and License live there instead of under WordPress’s Settings menu.

Share

Was this helpful?

Still stuck? Open a support ticket