Skip to content
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

UX: Clear cache options display on dashboard #25

Closed
reachcontent opened this issue Aug 7, 2015 · 8 comments
Closed

UX: Clear cache options display on dashboard #25

reachcontent opened this issue Aug 7, 2015 · 8 comments

Comments

@reachcontent
Copy link

Since adding the options to clear the cache in v0.2.0 they all display on top of the dashboard instead of a proper drop-down menu (broken?).
dashboardcacheoptions
NB: I manually upgraded later to latest Grav (0.9.35) since the upgrade button didn't work in the newer admin either (may be another issue): display glitch still here

@reachcontent reachcontent changed the title Clear cache options display on dashboard UX: Clear cache options display on dashboard Aug 7, 2015
@w00fz
Copy link
Member

w00fz commented Aug 7, 2015

Clear your browser cache, pretty sure that's all it is.

// Djamil Legato // From iPhone //

On Aug 7, 2015, at 03:44, reachcontent notifications@github.com wrote:

Since adding the options to clear the cache in v0.2.0 they all display on top of the dashboard instead of a proper drop-down menu.


Reply to this email directly or view it on GitHub.

@reachcontent
Copy link
Author

Nope, I just re-checked in another browser after I re-cleared the cache (and all private data) and it does the same.

@rhukster
Copy link
Member

rhukster commented Aug 7, 2015

It's definitely a css issue, do you have css pipelining on? I think this will effect admin also. We probably need to disable that in the administrator.

Clearing Assets Only cache would resolve that.

@reachcontent
Copy link
Author

I checked and CSS pipeline is off (I guess it is the default setting).
Could it be an issue with my provider's varnish cache as I experienced in the past for images?

@rhukster
Copy link
Member

rhukster commented Aug 7, 2015

i was able to confirm that css pipelining would cause this issue, and actually have already pushed a fix into develop branch that would resolve that. And yes it probably is varnish cache as that is quite aggressive and doesn't really know when CSS or JS files have changed unless you explicitly clear it or tell it something is updated.

You might want to try enabling the assets timestamps .. that might be enough to tell varnish that something has changed.

@reachcontent
Copy link
Author

Ok, thanks a lot!

@rhukster
Copy link
Member

rhukster commented Aug 7, 2015

Did that resolve your issue? If so can you close this?

@rhukster
Copy link
Member

rhukster commented Aug 9, 2015

Closing due to inactivity, please reopen if this remains an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants