Update

This guide is useful for PHPTRAVELS clients, travel agencies, developers, and website owners who want to keep their travel booking software updated, secure, and running smoothly.

This tutorial explains how to safely update your PHPTRAVELS script to the latest version. Watch the step-by-step YouTube guide to learn how to prepare your website, back up your files and database, upload the latest script files, run the update process, and test your travel booking website after the upgrade.

Update checklist in writing

Updating PHPTRAVELS brings security fixes and product improvements to your travel booking website. The video above walks through the whole process. Use the checklist below alongside it, and always test on a copy of the site first if you have customised code.

Before you update

1. Read what changed. Check the changelog on phptravels.com for the version you are moving to.

2. Back up your files. Download a full copy of the website folder, including uploads and any custom themes or modules.

3. Back up your database. Export it from phpMyAdmin or your hosting control panel and keep the file safe.

4. Note your settings. Keep your .env database settings and your Order ID handy.

5. Pick a quiet time. Update when few customers are booking, and consider showing a maintenance notice.

Run the update

1. Sign in to app.phptravels.com, open Orders and download the latest package for your order.

2. Upload the new script files to your server as shown in the video, keeping your configuration and uploads.

3. Run the update process shown in the video so the database is brought up to date.

4. Clear any server, browser or CDN cache.

Test after updating

• Log in to the admin panel and check that the licence is still active.

• Search and book a test product in each module you sell.

• Make a test payment with a gateway in development mode.

• Check that booking and payment emails still arrive.

• Open a few pages in a second language and currency.

Common problems

• 500 error after upload -- a file was not fully uploaded, or the database settings in .env changed. Re-upload and compare with your backup.

• Customisations disappeared -- custom code was overwritten. Restore it from your backup and merge it into the new version.

• Missing tables or columns -- the update step did not finish; run it again or restore the database backup.

• Licence asks to activate again -- enter your Order ID; see Activate Your License Key.

If anything fails, restore both backups and submit a ticket with your Order ID and the error.