Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
SimpleCache
SimpleCache
0
Comments
Given it's a 0.0.2 release, do you have further plans for developing the extension? What additions did you have in mind?
Anything that allows for 'object-level' caching of elements of a page would be very welcome if it were as easy as the role-based configuration that already exists.
It would great if I could just specify an object in the config file and then specify how long it's supposed to be cached.
I'm not familiar enough with Vanilla's order of execution to know if that's viable, but thought I'd throw the idea out there anyway...
If someone posts to a discussion, and my cache is set for 10 mins, does that mean it will be 10 mins until I see the updated discussion? This is how I assume a cache to work, but it doesn't appear to be behaving like that... I might be looking at things wrong.
Also how do you make it cache for both authenticated users and guests?
I believe a new comment will invalidate the existing cache, so it would be rebuilt on the next page load. It already caches for both authenticated and guests, since each may see a very different page.
Basically you'll just have to rename the settings_demo.php file to settings.php.
And no, sorry Wanderer, It is 'simple' because cache invalidation is only temporal. A cache file will
continue to be served until it expires, no matter if the data displayed is obsolete.
But yes, there are different files for different users, and one file for every guest (and different files for different requests of course).
Any chance that this can be ported to Vanilla 2?
There is a choice of built in caching support, but it may not all be fully functional, dirty, file, and mem.
Server level caching like micro caching on nginx
grep is your friend.
How does one turn this on in Vanilla 2?
Server level caching is always on here, but it works best is when the application does some caching itself to save on calls to the database and so serves what are basically static pages whenever possible. A good implementation of this is mediawiki.
Dirty cache doesn't do anything.
Note there is current a bug with file cache where it will break if php is in safemode. This is not to do with caching itself, but the file manager calling is_dir on folder that it doesn't have permission to check. This can be solve quite easily with a patch since, there is no need to recursively create folders, since php 5. I have made an issue on github.
I can't speak on effectiveness of the implementation, thought I have used the file cache independently quite effectively as pseudo transactional lock
grep is your friend.
Btw file cache the workaround would be to change
to something like
not ideal but most server should have ./ set correctly.
If it working then you should see folder in cache/Filecache
grep is your friend.