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

Cache policy

Started by Muut Archive 10 years ago · 6 replies · 370 views
10 years ago

Hi,

I'm just starting with Grav and it looks promising.
I have activated the admin plugin and when i enable cache in configuration, the admin part is impacted by the cache policy. For example, i have to wait some minutes before the new folders created appear. Only frontoffice should be impacted when enabling cache.

I have checked if my environnement (Mac os X with a vagrant VM and a NFS share) was the problem but it isn't.

The problem is really that expires meta send for admin page apply caching policy (so by default expires in 7 days).

10 years ago

By default Grav checks every single page load to see if something has changed, if it has, the cache is updated. Can you post a gist to your system.yaml so I can see what you have changed?

10 years ago

The other option is you have some webserver level cache configurations that is causing your browser to not even request new versions for 7 days.

10 years ago

It could be the last_modified and etag which you have turned on. Both of these tell the browser to not even look for changes. Set those both back to false.

10 years ago

Ok thanks for your response. So there is not way to have frontoffice pages using cache while admin pages do not have ?

Suggested topics

Topic Participants Replies Views Activity
Archive · by Deleted User, 9 years ago
0 1361 9 years ago
Archive · by Muut Archive, 9 years ago
2 939 9 years ago
Archive · by Muut Archive, 9 years ago
2 4069 9 years ago
Archive · by Muut Archive, 9 years ago
1 2958 9 years ago
Archive · by Muut Archive, 9 years ago
3 1123 9 years ago