Skip to content

Update DayTidy and Recover Safely

Update DayTidy through a controlled maintenance process. Free remains the required base plugin; Pro extends it and has separate authorization and update eligibility. An active plugin and authorized Pro use do not by themselves prove an update is available to the site.

  1. Read the changelog for the versions you plan to install.
  2. Back up both the WordPress database and files. Keep the previously working plugin packages and know how to restore the backup.
  3. Test the update on a staging copy that reflects the live site’s theme, payment approach, and enabled modules.
  4. Check DayTidy → Webilia Connect for Pro-use and update authorization when Pro is used.
  5. Plan a maintenance window if active customers could be affected.

Use a verified installation package rather than a source archive missing dependencies or built assets. Keep Free and Pro compatible; do not replace Free with Pro or install retired add-on packages as a normal paid setup.

Free updates are distributed through WordPress.org. The separately installed, active Pro plugin handles its own authorized update checks; Free does not download or install Pro. If Pro is missing, use Download DayTidy Pro in the Webilia Connect hub to open My Webilia, download the eligible ZIP, and install it through WordPress.

Use the available WordPress plugin update controls or upload the verified replacement package through WordPress’s plugin installer. If WordPress offers to replace the installed plugin, confirm the product and package before proceeding. Do not uninstall simply to replace its files.

After the update, confirm both required plugins are active, the expected modules remain enabled, and authorization states are correct. Follow the launch checklist for a public booking, resulting record, capacity, messages, and customer access. Validate configured payment integrations using the appropriate test environment.

If activation or a public page fails, record the exact error and version pair. Inspect DayTidy → Help & Support → System Status and Debug Info when the dashboard is available, and the site’s PHP logs when it is not. Review diagnostic output before sharing it; omit credentials and customer data.

Restore a known-good backup when necessary. Replacing plugin files alone may not reverse data changes made during an update, so use a coordinated database-and-files recovery plan. Preserve new live bookings created since the backup; involve the site maintainer before a rollback that would discard them.

Temporary deactivation is different from uninstall. DayTidy retains its business data on uninstall by default, but an administrator can explicitly enable Delete data on uninstall. Leave that destructive setting disabled for routine troubleshooting and updates. See General Settings and authorization recovery.