Skip to content

3.0.0-rc.3 — release candidate

Pre-release
Pre-release

Choose a tag to compare

View all tags
@wpgaurav wpgaurav released this 05 Sep 13:14
· 6 commits to main since this release
v3.0.0-rc.3
1870883

Release candidate. Not for production. This carries a one-way database migration to schema 1.2 — take a database backup before installing.

Install

Download the ZIP below and install it through Plugins → Add New → Upload Plugin, or:

wp plugin install page-blocks-builder-v3.0.0-rc.3.zip --force

Before you start

define( 'GT_PB_DISABLE_SECURITY_CHANNEL', true );  // stops the RC being swapped mid-test
define( 'GT_PB_ALLOW_PHP', true );                 // only if testing PHP blocks

Run the test site on pretty permalinks — on plain permalinks the library screen's REST calls fail. Known, fixed for final.

What to exercise, in order

  1. Upgrade a site that has PHP-enabled blocks and confirm they still render. The checksum scheme changed and old values are rewritten in the background; this is the highest-risk path.
  2. A page mixing page blocks with core blocks. Open the visual builder, type, save, reload — core and third-party blocks must survive, and the page must save twice in a row.
  3. A block using External File output. Edit its CSS and confirm the change reaches the front end. This never worked before 3.0.
  4. Detach a linked block in the block editor, edit the copy, and check the front end shows your version — fixed in rc.3.

New since rc.2

  • A block detached from the library kept rendering the library version. Fixed on both the editor and the server, so content already saved in that state is healed too.
  • tags and description are writable and round-trip over REST; both get fields on the edit screen.
  • Display Conditions are always visible, not only with a hook position set. Linked blocks get a respectConditions toggle, off by default.
  • New gt_pb_block_rendered filter, and a hooks reference in README.md.
  • CI syntax-checks assets/js — there is no bundler, so those files ship exactly as committed.

Going back

Reinstall v2.8.1. The database stays at schema 1.2, which is expected and harmless. PHP-enabled blocks strip their tags until re-saved. Full detail in README.md under "Going back from 3.0.0".

Reporting

Include the version from the Plugins screen (should read 3.0.0-rc.3), single vs multisite, and whether you upgraded or installed fresh. Security issues: see SECURITY.md.

Assets 3
Loading