PressPilot 2.4.0

PressPilot 2.4.0 — updates where WordPress already looks for them

Install: upload presspilot.zip (attached) via Plugins → Add New → Upload Plugin. Requires WordPress 5.8+ and PHP 7.4+.

Once this version is installed, future updates arrive on their own: new releases show up on Dashboard → Updates and the Plugins screen, just like any other plugin.

Updates from GitHub releases

• New releases are reported in the normal WordPress places, View version details shows these notes, and per-plugin auto-updates can be switched on.
• Built on the Update URI header, so WordPress asks GitHub instead of the wordpress.org directory — an unrelated plugin that happens to share the presspilot slug there can never be pushed over your install.
• A Check for updates link on the Plugins screen forces an immediate check. A good answer is cached for 6 hours; after a failure it backs off for 15 minutes, so an offline site never hammers GitHub.

Fix: block markup lost a level of backslashes on the way into the database

wp_insert_post() and wp_update_post() expect slashed data and unslash whatever they are given, so the escapes WordPress itself writes inside a block comment — \u002d\u002d for --, and the same for <, >, &, " — were stored with the backslash gone.

A class like is-section\u002d\u002ddark landed in the database as is-sectionu002du002ddark. It still rendered correctly, so the damage was invisible until someone opened the page in the block editor, where the class showed up mangled — and saving from there dropped the styling. The same applied to any JS, JSON or regex written through the API, which is why injected scripts previously had to avoid regex literals.

Content is now slashed on the way in, so what you send is what is stored. That workaround is no longer needed.

Also

• The build no longer sweeps up stray editor worktrees — a full nested copy of the plugin was being shipped inside the zip, doubling it from 227 KB to 464 KB.