Upgrade from 1.9.3.6 to 1.9.3.7

[Nexobus]

I am currently attempting to upgrade by site from 1.9.3.6 to 1.9.3.7 so that the latest security patches can be installed. When I uploaded the 1.9.3.7 files over the current installation, the entire site went to a 404 page error (store and admin).  And I was completely locked in. 

I reuploaded the 1.9.3.6 files and was able to get things working. However, what is different about the 1.9.3.7 version?  All files were uploaded correctly. So does anybody have any insights on how to deal with this issue???

[Tom Robertshaw]

Hi, have you read the release notes of 1.9.3.7? http://devdocs.magento.com/guides/m1x/ce19-ee114/ce1.9_release-notes.html#ce19-1936

There is a known issue in installations with PHP warnings being thrown, this can cause a 404 page being shown: http://devdocs.magento.com/guides/m1x/ce19-ee114/ce1.9_release-notes.html#ce19-1936

[Nexobus]

I have disabled every 3rd party modules, one by one, in hopes of identifying the module, yet the problem persists.  

What is the best way to identify the culprit?

Steve

[Meetanshi]

Hi @Nexobus,

Please check system.log file or exception.log file under var folder.

If you found any error than please share.

[Nexobus]

There is nothing listed in those 2 log files or any other log files.

[absolutedc]

This is caused when the core error handler is called early in the execution, when you're not in developer mode, before the current store has been initialised.

It's due to the addition of the log file extension validation in Mage.php, which in turn calls getStoreConfig, which refers to the current store.

We had a legacy store containing a module with an invalid config.xml - so try checking all your xml files to ensure they are valid.

It also should be easy enough to find by checking the stack trace around line 247 in functions.php (where the call to Mage::log is)

[Nexobus]

Can you provide a step by step guide to what you just wrote?  It is all greek to me.