Skip to content

WPPilot 1.4.1

Choose a tag to compare

View all tags
@wppilot-labs wppilot-labs released this 18 Aug 19:01
· 32 commits to main since this release
v1.4.1
1be92a6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Three defects, two of which let an agent report success for a change nobody could see. Recommended for everyone, and required if you also run WPPilot Pro.

Silent no-op on builder-owned pages

Elementor, Bricks and Beaver Builder keep their element tree in postmeta and render that instead of post_content, and they leave post_content looking like ordinary content. The existing marker guard only recognises proprietary syntax, so it never saw them.

Reproduced on Elementor 4.2.2 / WordPress 7.0.3 before the fix:

ability_returned : SUCCESS
updated_fields   : content
warnings         : (none)
canary_in_db               : YES
canary_VISIBLE_on_frontend : NO   <-- silent no-op

The write is now refused, naming the builder and — when installed — the ability that owns that builder's content. post_content still feeds RSS and search, so allow_raw_content_on_builder_post: true performs the write and returns an audit note recording that the rendered page did not change.

Ownership is value-exact rather than truthy, because both builders store a disabled state instead of deleting it: _elementor_edit_mode must equal builder, and a "0" flag is not ownership.

Divi, Etch and WPBakery needed no change — they store markup in post_content, where the markers already catch it. Breakdance keeps its own gate.

Builder storage-meta refusal named an ability that may not exist

It hardcoded "use the Elementor-specific abilities instead", which on a site without Pro points at an ability that is not registered there. It now routes through the same remedy helper the post_content refusal already used.

Version constant

WPPILOT_VERSION read 1.3.0 for the whole of the 1.4.0 release while the plugin header read 1.4.0. It drives the update check, admin asset cache-busting, and Pro's wppilot_min_version_satisfied().

Update WPPilot Pro to 1.1.2 alongside this

Pro shipped its own copies of 23 WordPress-core abilities before Free had them. Registration order follows plugin load order, which follows active_plugins — activation order, not alphabetical. On any site where Pro was activated first, Pro's copies registered first and won, so every fix Free shipped to those abilities since 1.1.0 was inert there, including this one.

Pro 1.1.2 stands aside when Free is 1.1.0 or newer. A site on an older Pro is unaffected.

Notes

No new abilities. No permission changes. Existing connections keep working and do not need re-authorising.

Install wppilot-1.4.1.zip below. The GitHub "Source code" archive is not installable.

430 unit tests, 686 assertions. Verified end-to-end on WordPress 7.0.3 / PHP 8.3.31 with Elementor 4.2.2, against the built artifact installed via wp plugin install.

Assets 3
Loading