cancel
Showing results for 
Search instead for 
Did you mean: 

Depency Problems after rolling back from broken 2.1.2 to 2.0.9

0 Kudos

Depency Problems after rolling back from broken 2.1.2 to 2.0.9

Feature request from grasdaggel, posted on GitHub Oct 14, 2016

Preconditions

  1. Used composer to upgrade to 2.1.2 (broken M2 version)
  2. Used composer to downgrade to working 2.0.9

Steps to reproduce

  1. Used composer to upgrade to 2.1.2 (broken M2 version)
  2. Used composer to downgrade to working 2.0.9
  3. deleted all temporary folders and did the setup:upgrade

Expected result

  1. Everything is working again

Actual result

This output:

Please upgrade your database: Run "bin/magento setup:upgrade" from the Magento root directory. 
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
Magento_Catalog schema: current version - 2.0.7, required version - 2.0.3
Magento_Catalog data: current version - 2.0.7, required version - 2.0.3
Magento_Search schema: current version - 2.0.4, required version - 2.0.1
Magento_Search data: current version - 2.0.4, required version - 2.0.1
Magento_Bundle schema: current version - 2.0.2, required version - 2.0.1
Magento_Bundle data: current version - 2.0.2, required version - 2.0.1
Magento_Downloadable schema: current version - 2.0.1, required version - 2.0.0
Magento_Downloadable data: current version - 2.0.1, required version - 2.0.0
Magento_Sales schema: current version - 2.0.3, required version - 2.0.1
Magento_Sales data: current version - 2.0.3, required version - 2.0.1
Magento_GroupedProduct schema: current version - 2.0.1, required version - 2.0.0
Magento_GroupedProduct data: current version - 2.0.1, required version - 2.0.0
Magento_CatalogRule schema: current version - 2.0.1, required version - 2.0.0
Magento_CatalogRule data: current version - 2.0.1, required version - 2.0.0
Magento_SalesRule schema: current version - 2.0.1, required version - 2.0.0
Magento_SalesRule data: current version - 2.0.1, required version - 2.0.0
Magento_Swatches schema: current version - 2.0.1, required version - 2.0.0
Magento_Swatches data: current version - 2.0.1, required version - 2.0.0
Magento_GiftMessage schema: current version - 2.0.1, required version - 2.0.0
Magento_GiftMessage data: current version - 2.0.1, required version - 2.0.0

Of course we did bin/magento setup:upgradeseveral times now.

2 Comments
New Member

Comment from grasdaggel, posted on GitHub Oct 14, 2016

Changing the respective fields in the database, now its throwing this error:

SQLSTATE[42S22]: Column not found: 1054 Unknown column 'synonym_for' in 'where clause', query was: (SELECT `mg_search_query`.* FROM `mg_search_query` WHERE (query_text = '') AND (store_id = '1') LIMIT 1) UNION ALL (SELECT `mg_search_query`.* FROM `mg_search_query` WHERE (synonym_for = '') AND (store_id = '1') LIMIT 1) LIMIT 1
#0 /home/atroposd/public_html/solicom/vendor/magento/framework/DB/Statement/Pdo/Mysql.php(95): Zend_Db_Statement_Pdo->_execute(Array)
New Member

Comment from sevos1984, posted on GitHub Oct 19, 2016

At the moment there is no possibility to downgrade, I'll mark this as improvement