New versions are listed in the changelog. Back up before every update. See what's new

Qdev Help Center

Help Center

Update safely

Back up, replace the files, run the update, then check the basics.

Back up first. An update replaces the product's files, so changes you made to them are lost. Keep your own changes under version control, and try the update on a staging copy when you can.

Envato emails you when a new version is out. Every product updates the same way:

  1. Read the release notes

    Open the changelog for the version you're moving to. New requirements and one-off steps are listed there.

  2. Back up

    Back up the database, the .env file, the storage/ folder and any files you changed.

  3. Replace the files

    Download the new archive from your Envato downloads, extract it, and copy the contents of its Script folder over your site's files. Keep your .env file.

  4. Run the update

    Open https://your-site.example/update and follow the update wizard. It applies the database changes the new version needs.

  5. Check the basics

    Sign in, send a test email, and try the main thing your site does.

Changed the code yourself?

Keep your version in Git, so an update becomes a merge instead of starting over:

  1. Keep the code in a private repository. A public copy of a paid product gets taken down.
  2. Keep your changes on their own branch.
  3. Add each new release to the main branch, then merge it into yours and resolve any conflicts.
  4. Deploy your merged version and run the update wizard as usual.

If something goes wrong

The installer appears after the update

The install marker in storage/app/ wasn't kept. Put your storage/ folder back from the backup.

A 500 error right after updating

Read the last error in storage/logs/laravel.log. Then check the PHP version the new release needs, that the files belong to the web server's user, and that .env was restored.