Free’s Demo Data tools distinguish the legacy sample from V1 Demo Packs. Demo Packs create visual hotel/catalogue content; they do not seed real bookings, guest transactions, payments or OTA reservations.
Choose the correct pack and environment
Use a disposable site first and obtain the ZIP from a trusted source. A checksum detects altered bytes; it does not establish the publisher or image rights. Verify the pack’s requirements against the actual Core and theme. Source code and demo photographs are separate assets; photographs are not bundled in the Free plugin package.
A presentation pack needs the matching active theme’s registered targets and allowed theme-license state. A content-only pack uses its narrower contract and cannot write menus or theme presentation settings; it does not require those presentation bindings. Do not assume every pack installs a complete themed homepage.
Preview before import
- Keep a verified files/database backup and open Hotel Booking → Demo Data → Demo Packs with the required administrator, upload and Page permissions.
- Upload the intended ZIP and review validation, site preflight, operations and warnings. The product limit is 64 MiB, further limited by the host.
- Resolve blocked site/theme/schema/currency conditions through their owning setup controls, then refresh the preview.
- Give the required visual-demo consent and production backup acknowledgement where applicable; start only the reviewed plan.
The importer does not overwrite persisted settings, even empty or false values. It does not activate a theme, change Reading settings, install licenses or enable gateways. Real rooms/data, an active installation or legacy ownership can block a fresh catalogue. Do not remove real bookings to bypass preflight.
Resume an interrupted import
Return to Continue import or Resume from checkpoint. If staging expired, re-upload the same logical content digest; a different pack is not an update of an in-progress run. Use Reconcile interrupted import for an uncertain intent. Unknown ownership stays needs-attention rather than creating duplicate objects by guessing.
Remove only proven owned content
Use Preview safe removal before Remove Demo Pack. User edits, marker changes, bookings and shared/referenced objects can block removal. Resolve references through their normal owner workflows and obtain a fresh preview.
Removal follows reverse dependencies; reused content and owner-managed system Pages are retained. It removes only still-matching setting leaves. An interrupted cleanup requires reconciliation and a new preview. There is no force-delete shortcut for unproven ownership. Save the authenticated diagnostic report and inspect remaining content before claiming clean removal.
