Update

This guide is for buyers updating an existing PropEngine installation.

Before Updating #

1. Create a full database backup.
2. Create a full file backup.
3. Confirm your current product version in the admin panel.
4. Review ../CHANGELOG.md.
5. If you customized product files, compare your changes before replacing files.

Updates should be tested on a staging copy first when the site is already public or business-critical.

Admin Update Flow #

1. Log in to the admin panel.
2. Open System & Settings > License & Updates.
3. Confirm that your license is active.
4. Check for updates.
5. Start the update only after backups are complete.
6. After the update finishes, review the public site and admin panel.

Manual Update Package #

Product owners generate update ZIP files with:

./bin/build-update.sh

or:

./bin/build-update.sh 1.0.2

The update ZIP contains production dependencies, compiled assets, a manifest, and the application files required by the update installer. It excludes local .env files, logs, caches, tests, development artifacts, old ZIP files, and local license-server workspace files.

After Updating #

• Clear application/browser caches if stale assets appear.
• Confirm admin login.
• Confirm property search and property detail pages.
• Confirm favorites, inquiries, contact forms, and localization.
• Confirm plugin pages and settings.
• Confirm scheduled jobs and queue workers if your installation uses them.

Troubleshooting #

• Update check fails: verify license activation, server connectivity, and update server configuration.
• Assets look old: clear caches and confirm the update package includes public/build/.
• Admin error after update: check PHP version, logs, and whether custom files conflict with the new release.
• Database issue: restore from backup, then retry on staging before production.