-
-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot scroll after update #965
Comments
We bet you are using cloudflare? #808 (comment) You should be able to disable an option as outlined by this other thread. |
I'm not - at least don't know about it. It worked just fine before the update. |
Try clearing your browser cache or try another browser. Actually nothing changed in this release that would change that behavior.
…--
Andy Miller
On February 11, 2017 at 07:09:51, Iva Pelc ***@***.******@***.***)) wrote:
I'm not - at least don't know about it. It worked just fine before the update.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub(#965 (comment)), or mute the thread(https://github.com/notifications/unsubscribe-auth/ABCNGYAC3hq-_hK0gtmC79WyR7RAQhZqks5rbcEvgaJpZM4L-JzK).
|
What's the URL of your site? |
Also, try the latest version that was just released with a JS bundle rebuild. Should sort it. |
Reinstalled whole Grav + Admin and everything worked fined until I switched language to "Czech". Then the problem occured again (no scroll; no Maintenance status on Dashboard; error after performing Check for updates). After switching back to "English" and clearing cache, it seems to work fine again, so the problem seems to be related to Czech translation... |
@ivapelc quick fix - edit user/plugins/admin/languages/cs.yaml like in here https://github.com/getgrav/grav-plugin-admin/pull/974/files I fixed this in the Admin plugin for the next release. |
I have fresh install of Grav + Admin. After todays upgrade of both Grav and Admin Plugin, I cannot scroll in the backend (no scrollbars)...
The text was updated successfully, but these errors were encountered: