ZOVANTA SOFTWARE / KNOWLEDGEBASE

Demo Manager 1.0.5 • inspected package; hosting/live validation not claimed

Demo Manager — current settings and requirements

Inspected build

Demo Manager 1.0.5, package key forovanta-demo-manager. Declared core requirement: >=1.0.0-beta.156p. Required core features: settings-checks-notice-v1, settings-screen-panels-v1. This is source documentation, not a fresh live-install certification. Preserve the package/data and read its update plan.

Private distribution: this package is owner/development tooling. Private does not by itself mean paid; follow its actual commercial flag and do not redistribute its code.

One screen: Add-ons → Demo Settings is authoritative. Underlying stored mode/interactive fields are compatibility details, not separate controls to edit manually. Advanced reset paths stay folded; a persistent demo leaves reset scheduling off.

Settings

The following labels/defaults come from the inspected manifest. The runtime may group or replace these controls with a dedicated screen; save through that screen.

Control Initial value Meaning
Demo Mode on false Off unless you turn it on. Installing or upgrading this add-on never turns it on by itself, and it stays off until this installation has been registered (the Authorized demo site URL above matches this board's address).
Demonstration mode "view_only" Stored value behind the visitor-experience selector. View-only remains the safe default, Interactive requires compatible core and uses its route policy, and Editable sandbox is the legacy limited action list. The unified Demo Settings screen writes this together with the interactive marker; both are kept for compatibility with boards and packages that read them. Choices: View-only — nothing is saved, Editable sandbox — permitted actions are saved and later reset.
Visitor experience "view_only" The one mode selector on Admin → Add-ons → Demo Settings: View-only, Interactive or Legacy sandbox. The screen maps it onto the stored mode and interactive marker in the safe order, so saving this cannot leave Interactive armed by accident. Choices: View-only — nothing a visitor does is saved, Interactive — visitors participate and their content is kept, Legacy sandbox — a short list of actions is saved.
Authorized demo site URL "" The address of THIS demonstration board, e.g. https://demos.example.com/forovanta . A reset refuses to run on any installation whose address does not match, so the tool cannot damage a real board even if its folder is copied.
Demo administrator username "" The account the "Enter as Admin" button signs in as. It is an ordinary account on this demo board; there is no demo password.
Demo member username "" The account the "Enter as Member" button signs in as.
Legacy sandbox — actions allowed "new_topic,reply,draft_save,group_join" Legacy sandbox only, shown as the four action checkboxes while Editable sandbox is selected. Full Interactive demo uses core route-aware permissions instead of this action-name list, so this field is hidden in Interactive and View-only and its saved value is kept. Do not add generic upload/delete actions to bypass restrictions.
Private state folder (outside the web root) "" Where the baseline, recovery backups, logs and the reset lock are kept. It MUST be outside the web root (e.g. /home/you/demo-state). Leave empty to use a folder beside the board's own folder named forovanta-demo-manager.
Production database name to refuse "" The name of the real board's database. If this demo's own database has that name, every reset refuses to run.
Demo uploads folder "" The uploads folder a reset restores (usually /uploads). Left empty, the board's own uploads folder is used.
Reset interval (hours) "24" How often the scheduled reset runs; the default is 24 hours. The schedule stays off until a valid baseline exists and you switch it on.
Scheduled reset on false Off unless you turn it on after a baseline exists. A permanent interactive demo leaves this off: visitor content is kept and the owner removes spam manually. This records your intent; the task itself is one entry in Panelica, whose exact command is shown on the Demo Manager page.
PHP executable (CLI) "" The PHP command-line binary the scheduled task runs, e.g. /usr/bin/php8.2. A bare name such as php is resolved from the shell's PATH. An FPM/CGI build (php-fpm) is refused, because it is a FastCGI server and cannot run a script. Left empty and undetectable, the Demo Manager page reports Not configured rather than printing a command that cannot work.
mysql executable "" The MySQL client used to restore the baseline, e.g. /usr/bin/mysql .
mysqldump executable "" The mysqldump used to capture the baseline, e.g. /usr/bin/mysqldump .

Install or update

Use the addon ZIP itself in Admin → Add-ons → Upload → Review → Install/Upgrade; addon.json belongs at its root. Do not upload the complete source/recovery bundle to core Package Manager. Back up database and private files, preserve existing settings/license/enabled state, and do not uninstall as an update step. After upgrading, test the actual member and staff operations, not just the new version label.

Current operating workflow · Shared addon installation

We suggest Panelica for managing your hosting environment.