Skip to content
Grav 2.0 is officially stable. Read the announcement →

Community guidelines

Please keep discussions civil and on-topic. Repeated violations may lead to a temporary ban.

Support

Disabled admin plugin, can't re-enable

Solved by Jona View solution

Started by Jona 5 years ago · 5 replies · 1276 views
5 years ago

Hello,

I had an issue updating the admin plugin of my website, when updating it complained about the directory of the admin plugin itself not being empty.
I disabled the admin plugin from de web interface, not realizing that this would trow me out.

I went to cli with the hope to be able to re-enable the plugin.
in the admin.yaml file the plugin is enabled. I tried reinstalling the plugin with gpm/install plugin, to no avail.

when I try to reach https://<myurl>/admin I get a 400 not found page.

How can I re-enable the admin plugin?

thanks,

Jona

5 years ago

A 400 error is odd. Is https:///admin a real thing?
400 Bad Request

The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing).

5 years ago

have you tried using the command line and doing

BASH
bin/gpm uninstall admin

or if on windows

BASH
php bin/gpm uninstall admin

then

BASH
 bin/grav install admin

again if on windows

BASH
php bin/grav install admin

With grav design, you can even just use a file manager and remove the admin directory and then reinstall it. HTH

5 years ago

I tried uninstalling using bin/gpm but the uninstall failed with the following error:

Cannot override frozen service "login".

I tried manually removing the admin folder from the user/plugins directory
and then reinstalling using /bin/gpm install admin (to no avail)
I tried installing using /bin/grav but that seems to be for grav skeletons, not for plugins, or am i mistaken?

thanks,

Jona

5 years ago Solution

I finally found and solved the issue,
apart from the admin.yaml file in user/plugins/admin/
there is an admin.yaml file in user/config/plugins/admin

this yaml file also holds a configuration option "enabled" to enable/disable the admin plugin, which was set to "false"
changing it to true resolved the issue.

👍 3

Suggested topics

Topic Participants Replies Views Activity
Support · by Thomas, 1 week ago
2 60 16 hours ago
Support · by Anna, 3 days ago
2 66 19 hours ago
Support · by Justin Young, 20 hours ago
1 34 19 hours ago
Support · by Duc , 1 week ago
2 70 6 days ago
Support · by Colin Hume, 1 week ago
2 61 6 days ago