Grav-plugin-admin: Server Error after Update to current stable

Created on 14 Dec 2016  路  2Comments  路  Source: getgrav/grav-plugin-admin

Hi there,

I've just updated grav and admin-plugin and got this error:

Server Error
Sorry, something went terribly wrong!

0 - The "Grav\Plugin\AdminTwigExtension" extension is not enabled in "dashboard.html.twig" at line 1.

For further details please review your logs/ folder, or enable displaying of errors in your system configuration.

The error went away after clearing the cache via grav-console.

bug

Most helpful comment

Yah, we've seen this very sporadically with this upgrade. Unfortunately it's appears to be a 'timing' issue with the way the new classes in the admin plugin get overwritten and then cached. We've actually added a slight 'pause' after installation in an attempt to resolve this for future updates, but because this is actually something that is happening based on the 'old' version of the admin, there's not a whole lot we can do. Also it's very hard for us to reproduce. Performing the same steps with a consistent base install, sometimes causes it and sometimes not.

Anyway, as you say, a clearing of cache does fix it. Also if you can't reach the CLI for some reason then going to /admin/dashboard/task:clearCache results in a page that does render (although you will get a missing security token message), but from there you can click the Clear Cache button in the admin, which fixes it also.

All 2 comments

Yah, we've seen this very sporadically with this upgrade. Unfortunately it's appears to be a 'timing' issue with the way the new classes in the admin plugin get overwritten and then cached. We've actually added a slight 'pause' after installation in an attempt to resolve this for future updates, but because this is actually something that is happening based on the 'old' version of the admin, there's not a whole lot we can do. Also it's very hard for us to reproduce. Performing the same steps with a consistent base install, sometimes causes it and sometimes not.

Anyway, as you say, a clearing of cache does fix it. Also if you can't reach the CLI for some reason then going to /admin/dashboard/task:clearCache results in a page that does render (although you will get a missing security token message), but from there you can click the Clear Cache button in the admin, which fixes it also.

I, too, fell prey to this on a 1.17 -> 1.2 upgrade. Clearing cache as outlined in previous step, then continuing to check updates (again) and then actually performing them allowed me to continue.

Thanks!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

danzinger picture danzinger  路  5Comments

maciejmatu picture maciejmatu  路  3Comments

ritchiedalto picture ritchiedalto  路  6Comments

dimayakovlev picture dimayakovlev  路  5Comments

illycz picture illycz  路  5Comments