Site crashing following 5.5.2.1 ---> 5.6.0 upgrade
Permalink
I just made multiple attempts to upgrade our system from 5.5.2.1 to 5.6.0. No errors occurred during the upgrade, but now all the pages are crashing with the following error:
The error itself is understandable: there is no ../concrete/helpers/concrete_file.php present in the system. However there IS a file ../concrete/helpers/concrete/file.php.
I plugged in my debugger. Here's what I found so far:
- The helper function in loader.php (helper($file, $pkgHandle = false)) is getting passed the correct file name, "concrete/file.php".
- It isn't until after the require_once statement that the file name is somehow magically transformed into "concrete_file.php".
- It has something to go with the class name getting parsed to remove its camel caps.
I'm still picking through code, but if anyone else is familiar with this issue, I'd be grateful for any info that might speed things along to a solution.
Thanks!
Warning: require_once(<path-to-site-document-root>\public_html\content\updates\concrete5.6.0\concrete/helpers/concrete_file.php): failed to open stream: No such file or directory in E:\inetpub\wwwroot\test.landoll.com\public_html\content\updates\concrete5.6.0\concrete\core\libraries\loader.php on line 279
The error itself is understandable: there is no ../concrete/helpers/concrete_file.php present in the system. However there IS a file ../concrete/helpers/concrete/file.php.
I plugged in my debugger. Here's what I found so far:
- The helper function in loader.php (helper($file, $pkgHandle = false)) is getting passed the correct file name, "concrete/file.php".
- It isn't until after the require_once statement that the file name is somehow magically transformed into "concrete_file.php".
- It has something to go with the class name getting parsed to remove its camel caps.
I'm still picking through code, but if anyone else is familiar with this issue, I'd be grateful for any info that might speed things along to a solution.
Thanks!
When I upgraded the system, that file became obsolete, and was not "playing nice" with the new loader. Since the new version of C5 contained a permanent fix for the ff multiple upload issue, the solution was just to remove that file.
Note to self: If an upgrade breaks something, checking all the custom overrides should be one of the first things on my list of troubleshooting steps.