Jump to content
thirty bees forum
  • 0

Doing an "Update all modules" caused backoffice to throw "500 server Error" when trying to access "Modules and Services" menus.


papagino

Question

Hello people.

After doing an "Update all modules" in my backoffice, it shows "500 server Error" when trying to access the Modules and Services, Preferences/Core Updater, Advanced Parameters/Performance and Administration/Permissions menus.

I'm on Thirty Bees 1.4.0 running under PHP 7.4.

I changed "define('_PS_MODE_DEV_', true);" in defines.inc.php, but no errors are showing when I get the "500 server Error" page.

My site is now in Maintenance mode.

Any ideas on how to fix this?

Thanks

Dan

Edited by papagino
Link to comment
Share on other sites

4 answers to this question

Recommended Posts

  • 0
4 minutes ago, the.rampage.rado said:

I imagine you're unable to go to Modules page?

If so can you track your error log and post the latest entries there? It's located in your root folder.

When looking at the Log files for today, I see this one:

*ERROR*     2023/04/20 - 13:17:12: Fatal Error: require_once(): Failed opening required '.../modules/coreupdater/classes/Settings.php'

If I open the folder under /modules/coreupdater/classes/, there is no Settings.php file, only these 2 folders.

Why is this?

71908286_MissingSettingsphpfile.thumb.png.487db5a9c5deaf198c8d87db13cc9ab4.png

Link to comment
Share on other sites

  • 0

Can you try to delete the whole coreupdater folder? Please, back it up firstly!

 

Then try to access your BO->Modules

Probably coreupdater was part of the update and you faced some issue and the update did not complete fully.

If you have access to Modules, install coreupdater and proceed with the needed updates (system and modules) if aplicable.

This folder contents are as follows:
image.png.8b3670be3d063ba4b88fd233ab0e6efc.png

Edited by the.rampage.rado
Link to comment
Share on other sites

  • 0
6 minutes ago, the.rampage.rado said:

Can you try to delete the whole coreupdater folder? Please, back it up firstly!

 

Then try to access your BO->Modules

Probably coreupdater was part of the update and you faced some issue and the update did not complete fully.

If you have access to Modules, install coreupdater and proceed with the needed updates (system and modules) if aplicable.

This folder contents are as follows:
image.png.8b3670be3d063ba4b88fd233ab0e6efc.png

Doing it now, seems to be working...

I believe that coreupdater was part of the modules that needed to be updated...

Done...

Thank you, this fixed the problem, all good now.

Cheers

😉

 

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...