Core Forms 4.2.0-beta7
Pre-release. Hot-fix for the WSOD that affected beta5 and beta6.
What was wrong
Beta5 added an init-action callback registered as `'Core_Forms\_cf_wire_revisions'`. But `src/functions.php` doesn't declare a namespace — every function in it (`cf_get_form`, `cf_get_settings`, `_cf_wire_revisions`, etc.) lives in the global namespace despite the `use Core_Forms\Form;` at the top of the file.
The namespaced callback string resolved to nothing, and at init time WordPress fataled with \"function not found\" — taking the admin (and depending on cache state, the whole site) down.
Beta6's `function_exists('add_action')` guard helped CLI tools (PHPUnit, PHPStan, dump-autoload) load `functions.php` without fataling, but never addressed the runtime fatal. Sites running beta5 or beta6 still saw the WSOD.
What's fixed
The init callback is now registered as plain `'_cf_wire_revisions'`.
Verified on a live install: - Plugin active at 4.2.0-beta7 - Frontend `200` - Admin `302` (login redirect — no fatal) - `php -r 'require autoload.php; var_dump(function_exists(\"_cf_wire_revisions\"));' → bool(true)`
Upgrade strategy
If you tested beta5 or beta6 and hit a blank screen, this is your fix. Download the attached zip and upload via Plugins → Add New → Upload — WordPress will replace your existing install.
Everything else from the beta5/beta6 release notes (analytics tab, revisions tab, CF7 migration, WhatsApp actions, security hardening) is intact and unchanged.