Error 500 after Upgrade to 4.6.12

[_Vault_]

My site is down after upgrading to 4.6.12. Upgrade went smooth, no issues reported but now the site is completely down. I found this error in the php log:

 

[05-Apr-2022 19:17:49 UTC] PHP Fatal error:  Cannot use "parent" when current class scope has no parent in /srv/http/root/html/system/Theme/Theme.php(2632) : eval()'d code on line 37
 

[Adriano Faria]

1 minute ago, _Vault_ said:

[05-Apr-2022 19:17:49 UTC] PHP Fatal error:  Cannot use "parent" when current class scope has no parent in /srv/http/root/html/system/Theme/Theme.php(2632) : eval()'d code on line 37

Enter with RECOVERY MODE and disable plugins and apps. One of them isn't updated to PHP 8 yet.

 

[Jim M]

Please try recovery mode as Adriano suggested and let us know if that helps.

[_Vault_]

Thanks!

When I activate Recovery Mode, the site loads, but it's preventing ACP Access:

1S107/3 Before you are able to use the Admin Control Panel, you must edit 'constants.php' and remove the following line:
define( 'RECOVERY_MODE', TRUE );

But I have to go to ACP to put the site "Offline" and disable the plugins one by one or?

 

- 

 

Edit: Forget it, after removing the line I can now acces the ACP again. I'll now check whats going on. Cheers!

Edited April 5, 2022 by _Vault_

[Jim M]

You will want to hit the ACP at the root, on the default software this would be /admin but you will need to go directly to your admin's modified folder name. Often you will get this error if you try and use an existing session or go to a different page.

If you're still having issues, please update the access details in the Client Area and we can take a look.

[_Vault_]

Thank you both @Jim M and @Adriano Faria for the tip with the recovery mode and how to use it.

The plugin causing the error was:

Back To Top  1.0.5
By Pete Treanor

http://invisionfocus.com

After enabling the plugins one by one, and clearing the cache after each one, I was able to identify it. Luckily it's one that I can easily spare.

 

Thanks again! 🙂

Edited April 5, 2022 by _Vault_

[Jim M]

Glad to hear you've found the issue.