I was just updating an add-on (Structure) via FTP and when I went to log in to update via the Add-Ons section, I keep getting a “This page isn’t working” 500 error but only on that section. Everything else works perfectly. I’m a little stumped on this one. Any help would be greatly appreciated.
Thanks in advance,
Thanks, I have enabled debugging but I’m not seeing any data being displayed. Obviously, not on the error page, but also not in the CMS once I go back and click around. I loaded up Chrome’s Inspect and did see the following in the Console:
Failed to load resource: the server responded with a status of 500 () VM82:5551 crbug/1173575, non-JS module files deprecated.
so you have
$debug = 1; in your admin.php (assuming you’re using admin.php), but still getting the browser default 500 error message rather than a PHP error?
Next, I’d check your server’s error log for that site to see if there are errors logged there.
Of course, start with just deleting the structure files and trying to copy the files over again to make sure something didn’t get corrupted. you might even try re-downloading and extracting again.
> so you have $debug = 1; in your admin.php (assuming you’re using admin.php), but still getting the browser default 500 error message rather than a PHP error?
After renaming the Structures folders in all locations with a simple underscore before the folder name, things got interesting.
AREA: SYSTEM/USER/ADDONS WHEN OLDER VERSION ENABLED - InvalidArgumentException Caught No such property: 'session' on ExpressionEngine\Legacy\Facade Facade.php:128 WHEN PREVIOUS VERSION ENABLED - error Unable to load the following extension file: ext.structure.php WHEN LATEST VERSION ENABLED - HTTP ERROR 500
Well, the older and the previous versions make sense. You should get the
Unable to load the following extension file:
ext.structure.php on the latest version as well if you rename the add-on folder.
We’re you able to check the server error logs and see if anything was in there? Somehow you need to find out what the error is that is causing the 500.
You might also try dev tools in chrome.