Error after Updating Plugins

Hello there,

I've accidentally tried to update the plugins in a installed GRAV (1.1.8). As a result I get the following error while calling the admin section.

"An exception has been thrown during the rendering of a template ("file_exists(): open_basedir restriction in effect. File(/customers/f/9/e/<site>/httpd.wwwuser/plugins/admin/themes/grav/c ss-compiled/nucleus.css) is not within the allowed path(s): (//customers/f/9/e/<site>//httpd.www://customers/f/9/e/<site>//httpd.private://customers/f/9/e/<site>//tmp:/customers/<site>/<site>:/var/www/diagnostics:/usr/share/php)") in "partials/base.html.twig" at line 21."

What can I do to make it work again????

Regards,

Michael

Looks like the path inside ...

file_exists(): open_basedir restriction in effect. File(/customers/f/9/e/<site>/httpd.wwwuser/plugins/admin/themes/grav/c ss-compiled/nucleus.css)

is broken. Can I fix it somehow?

Sorry, the version is 1.0.10.

Hi, this looks like a problem caused by the hosting provider as they have open_basedir restriction in effect as the error says. You might want to ask your hosting support how to fix this.

I looked up the same solution but it really looks like the link is broken
theres an "/" missing between www and user

I tried putting a site under httpd.www to check if the dot in the root folder name causes an issue but I have no problems - looks like some hosting misconfiguration but not sure what to suggest

I'm lucky. Found an older backup of the page and updated it in the correct way and no errors occured. So the error is a result of updating the plugins before updating the core of grav...

Indeed. You should always do a selfupgrade before update.

the update happend in the admin plugin not in cli. ;) But yes now I learned it the hardway. Somekind of warning or an automatic abort would be nice.

Good point. I'll do a PR.

Ah ok thank you. ( PR is some kind of ticket in github ???) ;)

Oh. A pull request, yes. I'll update the update command to warn you if a new version of Grav is available. We'll see if the dev team thinks it's helpful.

I think it is. I repaired the page for a client. He isn't that type of computer geek. So he accidently destroyed the hole page. XD But I think it could happend to anyone.

PR submitted.

yay thank you ;)

It only applies to the CLI, though. I have no idea how the Admin plugin handles this.