Skip to content

Commit

Permalink
Merge pull request #1798 from Quetzacoalt91/add-faq-about-PS_VERSION_DB
Browse files Browse the repository at this point in the history
Add explanation about PS_VERSION_DB mismatch
  • Loading branch information
kpodemski authored May 6, 2024
2 parents 7f6802f + c58dd4a commit 3b9e3c9
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions faq/upgrade.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,3 +32,13 @@ If during upgrade process, it fails with the error message:
This error message indicates something went wrong on server side.

In order to find out what exactly went wrong, you need to check the upgrade process logs that are located into the folder `{Prestashop_Folder}/{Admin_folder}/autoupgrade/tmp/`

## The version of PrestaShop does not match the one stored in database

**Q:** Upgrade cannot start because the error "The version of PrestaShop stored in database does not match the running code. Your database structure may not be up-to-date and/or the value of PS_VERSION_DB needs to be updated in the configuration table." is displayed.

**A:** In PrestaShop, `PS_VERSION_DB` is a constant that holds the current version number of your PrestaShop database schema. The main purpose of `PS_VERSION_DB` is to keep track of the database schema's version history. When you upgrade a shop, the database schema is modified to match the structure of the new version (e.g. add or remove tables, columns, or relationships).

Before upgrading PrestaShop, the upgrade module relies on this constant to ensure that the current version matches the database schema. If the values don't match, it would be a sign of potential issues with the database structure or data which could lead to unforeseen consequences during the upgrade process.

To resolve this issue, run the database upgrade step as explained in [the upgrade page]({{< ref "/8/basics/keeping-up-to-date/upgrade#database-upgrade" >}}).

0 comments on commit 3b9e3c9

Please sign in to comment.