Total Posts: 29
Yorkshire, England, Great Britain, United Kingdom
How did you perform the upgrade?
I would verify the integrity of your magento 188.8.131.52 installation by downloading one of the magento-184.108.40.206 archives, and extracting this into the root of your magento installation.
If you have been using magento correctly, no core files should be modified, and this should pose no problem.
Of course always perform a backup before any changes.
Doing the above will(should) not break anything as all your custom installed themes and installed extensions will continue to exist.
your /app/etc/local.xml will not be overwritten, so all install data (database) etc will remain as is, meaning your magento install will still work as is.
The only one to take care of is your .htaccess file, for any custom modifications and redirects you may have placed in it.
After copying the main magento onto yours, you should now have a full 220.127.116.11 installation. Any issues arising now, are down to extensions, things you’ve changed, or files remaining from the old 18.104.22.168 install, these should be removed, and this can be found by using the .diff files provided on the download page, or downloading a fresh magento-22.214.171.124 and magento-126.96.36.199 and comparing the folders with the tool of your choice (I don’t recommend manually as you will be doing it for days).
Remove any old magento-188.8.131.52 files from your installation (as they are obviously not needed)
After this, you will have verified nothing is modified in the core / default files with your installation and that no magento-184.108.40.206 files could be causing conflict.
You can then perform detailed analysis on your database integrity (using the db-repair-tool etc) and hopefully work to get your issue resolved.
Hope the above helps, but if issues are caused with an upgrade, I verify the upgrade first, rather than looking at files from exception reports and system logs, these are to look at after, if the problem still persists.