Jump to content

"Module Manager" area/page ERROR 500


Recommended Posts

Hi everyone!! I went to update a new module yesterday and the update failed. Since then and to my surprise I cannot access the module manager area at all and I get thrown the following:

Quote

The server returned a "500 Internal Server Error".

Upon starting debug mode and heading to the module page I get:

Quote

ClassNotFoundException

HTTP 500 Internal Server Error

Attempted to load class "FormModifier" from namespace "PrestaShop\Module\FacetedSearch\Form\Feature".
Did you forget a "use" statement for "PrestaShop\Module\FacetedSearch\Form\Feature\FormModifier"?

in modules/ps_facetedsearch/src/Hook/Feature.php (line 53) with the following result

Quote

    public function __construct(Ps_Facetedsearch $module)

    {

        parent::__construct($module);

        $this->formModifier = new FormModifier($module->getContext());

        $this->dataProvider = new FormDataProvider($module->getDatabase());

    }

    const AVAILABLE_HOOKS = [

        'actionFeatureSave',

 

Anyone have any ideas? Any help would be much appreciated! Thanks Y'all

Edited by Kristian Bowler (see edit history)
Link to comment
Share on other sites

1 hour ago, Kristian Bowler said:

Unsure if this helps at all

snip.JPG

 

1 hour ago, Kristian Bowler said:

Unsure if this helps at all

snip.JPG

Hi Kristian 

For the php exception error you have to open up that Feature.php file and edit it so first check if you're importing the class at the top of the script.

For example (use Your/Class/Here). 

Link to comment
Share on other sites

*******FIXED******
For anyone wondering or reading this I have managed to fix this. I got this error because I clicked "update" on the modules page and then my modules manager section of BO crashed.

I renamed /modules/ps_facetedsearch to something random like "ps_facetedsearchOLD" and re-uploaded this file via FTP:

 

Quote

Once uploaded faceted search should show up in your modules list again but requiring an update. Click "update" (I know risky right lol) and this time it should complete successfully. Voila! All fixed :)  

Edited by Kristian Bowler (see edit history)
  • 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...