Builderius 1.6 RC-2 Release Notes

November 11, 2026

Release Candidate 2

This release fixes security and privacy issues, publishing and caching problems, and builder bugs found since RC-1. We recommend updating every site.

One fix changes what existing sites render: a dynamic data value of 0 now shows as 0 instead of nothing. Read Rendering and dynamic data before you update.

Security and privacy

The page cache could store pages that belong to one visitor and serve them to other visitors. This release closes that gap and several others.

Fixed: A broken cookie comparison gave every anonymous visitor who carried any cookie the same cached copy of each page. Cart counts, pending comment notices, and password-protected posts unlocked by one visitor could reach the next visitor. Pages that belong to a specific visitor are no longer cached.

Fixed: A page rendered with “Preview as” was saved under the public cache key and served to the next anonymous visitor, including the admin bar.

Fixed: Anyone could add ?clear-builderius-cache to any URL, without a permission check. It wipes the compiled service container and compiled templates, so anyone could force a site to keep rebuilding them. It now requires the Builderius developer capability.

Fixed: Browsers could reach the Builderius cache directory under uploads. That included the compiled service container, compiled templates, and developer PHP stored in the builder’s preview scratch. Browsers are now denied access, and the object pool now sits in a directory whose name comes from a site secret.

Fixed: Sense AI endpoints responded on unlicensed sites. Saving settings, installing an MCP server, creating a WordPress application password and reading bridge diagnostics all worked while the settings tab said a valid licence was required.

Publishing and caching

Fixed: A page rendered while a release was publishing could stay cached for ten hours. Cache entries written before a publish can no longer be served after it.

Fixed: Generated CSS and JS kept their old ?ver= value after being rewritten, so browsers and CDNs served stale files after each publish. The version now comes from the file’s content.

Fixed: Publishing a commit group did not regenerate JS, so an edited snippet kept serving its old file.

Fixed: Depending on the order two listeners ran in, generating assets could delete a component’s JS and never write it back.

Fixed: Builderius cleared the entire object cache in six places. On Redis or Memcached installs, this dropped every other plugin’s cached data for the whole site.

Fixed: Serving a cached page no longer costs four database queries.

Fixed: If the cache directory was cleared by hand, it stayed without its IIS and directory listing guards. They are now restored.

Builder

Fixed: Keyboard shortcuts stopped working once an element was selected on the canvas, which is how most elements get selected. Ctrl+Shift+D opened the browser’s “bookmark all tabs” dialog instead of duplicating, and Ctrl+C, Ctrl+Z and Esc did nothing.

Fixed: Redo with Ctrl+Shift+Z now works, in every panel and on every platform. It had never worked before.

Fixed: On wide screens, the canvas ignored a width you dragged or typed until a breakpoint snapped in, and the base breakpoint reported a width the canvas did not have.

Rendering and dynamic data

Changed: A dynamic data value of 0 used to render as nothing, so a count could not be compared against zero. It now renders as 0. This changes output on existing sites: any binding that currently shows nothing for zero will start showing 0. Existing ? 'yes' : 'no' workarounds keep working.

Fixed: A rendering condition inside a component placed in a Collection is now evaluated for each row. Before, it was evaluated once against an unresolved {{ field }} placeholder, so it was always true.

Fixed: Two data variables that shared a root field name returned each other’s values.

Fixed: Logged-out page views no longer log an error for each user field that a logged-out visitor doesn’t have.

Added: When a data variable field resolves to nothing, Builderius now logs one line per query that names each failed path and the reason it failed.

Licensing

Fixed: If an activation was blocked before it reached the licensing server, it now completes through the update check, which the same protections allow through. Some sites ran licensed for months while their activation records still said they had never been activated.

Added: Licensed sites now check once a day that their licence still covers them, so removing a site in your account takes effect. Before this, a removed site could keep every paid feature.

Fixed: A site whose activation was intercepted showed as valid but had every paid feature turned off. The update check now keeps the entitlements it already receives.

Fixed: Licence messages said “Builderius PRO” on every edition, including two editions that never had that name.

Fixed: After you activated a licence, the other settings tabs kept saying a licence was required until you reloaded the page.

Fixed: After an update, a site could offer an update to the version it had just installed, for up to twelve hours.

Updating

Update as usual. If any of your bindings rely on a zero value showing as empty, check those pages after you update, because they will now show 0.

Avatar9
Builderius Team

Ready to build like a professional?

Transform your WordPress workflow with professional-grade visual development. No more compromising between speed and quality.