Oxwall · English / Nederlands ✦

Technology and digital projects

A theme change needs a restore test, not just a backup filename.

For Dutch Oxwall users and Ontwerpers, the useful question is whether the site can be restored with its data and uploads intact. A copy of the theme alone does not establish that.

This pre-change plan keeps the test away from the live site and makes the acceptance checks explicit.

Record what belongs to this installation

Start with versions and storage locations, not a generic command.

Oxwall’s own migration documentation distinguishes database backup, site files and configuration. Its instructions are old, so use it to identify components and verify the procedure against your installed version and hosting environment.

Include the database, uploaded files, application and plugin/theme files, plus configuration needed for restoration. Protect backups containing personal data or credentials; do not put them in a public web directory.

A restore packet to verify

A restore packet to verify
PartWhat the administrator records
ApplicationExact Oxwall version, installed plugins and active theme.
DatabaseBackup timestamp, database version and how consistency was obtained.
UploadsActual storage locations and whether they are local or external.
ConfigurationEnvironment settings and required secrets held through an approved secure route.
Test destinationA separate environment with outgoing messages and scheduled side effects controlled.

Restore before you change the theme

A homepage alone is a weak acceptance check.

Illustrative restore check

Use an authorised test account and non-sensitive test content. Confirm that the account can sign in, open a known upload and follow a representative content link.

Compare an agreed sample of records and uploaded-file counts with the source backup. Record any missing item rather than assuming the new theme caused it.

Only after the baseline restore works, apply the proposed theme in that test environment and repeat the same checks.

Give rollback a clear owner and stopping point

English or Nederlands, the handoff should mean the same thing.

Write the go/no-go decision beside the test results. “Backup completed” and “restoration verified” are different states; do not compress them into one tick.

Agree who can restore production, what downtime is acceptable and which new changes could be lost after the backup point. A theme preview is not permission to overwrite the live database.

Keep a short bilingual handoff if the team needs it: backup gemaakt records creation; herstel getest records a completed restore test. Add the date and the person who actually performed each step.

External guides and references

Open the source for the part you want to examine further.