1

I'm a little stuck when i started om my project i cloned the Magento2 dev repo instead of composer or manual instal..

Now i want to sort this out since my project is almost going live but still on 2.0.0. When i create a clean install i get the following error

The following modules are outdated:
Magento_Theme schema: current version - 2.0.1, required version - 2.0.0
Magento_Theme data: current version - 2.0.1, required version - 2.0.0
Magento_Customer schema: current version - 2.0.7, required version - 2.0.6
Magento_Customer data: current version - 2.0.7, required version - 2.0.6
Magento_Cms schema: current version - 2.0.1, required version - 2.0.0
Magento_Cms data: current version - 2.0.1, required version - 2.0.0
.....

This is just een excerpt many more modules.. Am i mising something?

1 Answer 1

1

your Problem is, that the database has newer Versions of the Schema then your actual modules have.

The Theme Module for example. In your Database, 2.0.1 is installed while your code is 2.0.0.

Since 2.0.0 is the current version in the 2.0 branch and 2.0.1 the current version in the develop branch it seems like you cloned Magento2 and checked out the develop branch, installed it and then checked out the 2.0 branch (or maybe the 2.0.6 Tag for example)

Since there is no downgrade functionality I think you have to reinstall Magento from the correct source code Version.

7
  • Thats actually what I did. I think it's a little bit the way around. I installed now the correct one. But since my database is coming from the develop branch my db is 2.0.1 while the code is 2.0.0. Is there a way of just changing values in the db. Or will that screw up things very badly? May 22, 2016 at 19:19
  • the problem is that the install scripts for the newer versions already ran and altered your database. It is possible to change the values in the setup_module table. It's very likely to cause unpredictable behaviour since your code relies on a different db schema. Also it will break if you later really want to upgrade your magento instance, because the update scripts already ran but due to the manipulation in the table will be executed again May 22, 2016 at 19:24
  • Do you suggest to fresh install export import products and configurations? May 22, 2016 at 19:26
  • yes I think this would be the best solution for you May 22, 2016 at 19:26
  • you could also think about export -> import complete tables if you compare them first and they have the same structure (for tables that are not covered by the magento import/export module) May 22, 2016 at 19:28

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.