ZOVANTA SOFTWARE / KNOWLEDGEBASE

Beta Access Pro • 1.0.0-beta.2 • development preview

Beta Access Pro release status and recovery

1.0.0-beta.2 remains a Premium development preview, not a production-approved core replacement. Its migration receipt says core_removal_ready=false. The original target is supplied starter 155w; do not infer runtime compatibility with 156j from documentation alone.

The native installer is Beta-Access-Pro-1.0.0-beta.2.zip, with addon.json at its root. Use a staging clone, a complete file/database backup and a legitimate core-supported product/master entitlement. Upload through Admin → Add-ons and complete the install/update action so the schema callback executes. Do not uninstall or delete tables to update.

It implements one program, text branding, up to ten questions, acceptance terms, closed-by-default applications, optional automatic approval of new submissions, manual review, tester membership grants/removals, per-member page status, audit events and stale-form protection. It additively creates four bap_* tables and adopts the existing category/group/memberships with a snapshot and receipt. It does not invent old answers or acceptance timestamps.

Beta.2 supplies a description, five questions and terms to new programs. Existing blank content is filled once during installation/update; custom content survives. The content-defaults-v1 receipt preserves the prior configuration and prevents refilling intentionally cleared fields on later reinstalls. Existing applicants are not recorded as accepting new terms.

Manage testers through one UI during staging. The old core switch changes the same group but does not synchronize add-on application/audit rows. No verified ownership handoff permits deleting that core feature yet. Source/static checks are not executable PHP/MySQL/HTTP/license/browser acceptance; exact-package runtime and ACL recovery verification remain outstanding.

The inherited discussion matrix allows registered members to read and testers to post. Other groups and staff can grant additional access. Removing tester membership does not revoke independent grants. Do not advertise tester-only confidentiality without reviewing the actual ACL.

Disable/remove preserves category, permissions, group memberships and add-on records. To undo later add-on actions, restore a verified staging backup rather than replaying an old adoption snapshot over newer data. Keep all legacy and bap_* tables.

Not supplied: image/logo upload, color branding, invitations, email delivery, arbitrary-page/download restrictions, multiple programs, configurable category/group selectors, reapplication/retention/export UI and automated migration reconciliation. Status appears on the program page. Do not market these as finished features.