you state on your plugin write up that you cant think of a single wordpress website that shouldnt use zencache, does this include websites built as social networks?
That is correct. ZenCache will work even on sites like what you describe here. ZenCache Pro includes Logged-In User Caching functionality that will work great with something like BuddyPress, where many of your users are logged-in.
The plugin also supports Custom Post-Types, so those will be cached and the cache for that Custom Post Type post cleared automatically when the post is updated.
Regarding widgets: Right now we have a bug report open related to this: When a widget is updated, the cache is not cleared, so you’d need to manually clear the cache after updating a widget.
We also have a feature request open that will allow you to specify specific URIs that should be cleared whenever a post is updated. This will be useful if, for example, you have a widget that shows the most recent comments: you would want to tell ZenCache to clear the page that includes that widget whenever a new comment is posted. This isn’t possible at the moment, but it’s coming soon. 🙂
Hi raamdev it sounds great but there is one problem. Seeing as users update posts at an extremely fast rate and my widgets are set to auto refresh every minute then how could this possibly work?
The example used above was only for the comments. There is alot more to it and other widgets need updating regularly to, Let me explain more..
Say if my site is user intensive and lets just use the comments widget as an example again, then in the space of say an hour or so there could be 100s of comments made, so how could i clear that page cache 100s of times every hour? This would mean sitting at the computer like a robot 24 hours a day solid to just to clear cache everytime comments or other widgets that rely on this feature.
So this leads to my next question, Would it not be better to include some kind of exclusion in the backend that will let you tell Zencache not to cache these widgets?
thx
Oh one more thing
We also have a feature request open that will allow you to specify specific URIs that should be cleared whenever a post is updated
This is a great idea but how would this apply to buddypress internal pages based on the users id? example: on the users profile pages and groups etc? how would you include these URIs?
Sorry about all the questions but i am a very deep thinker and always think about a scenario when using a new plugin before dedicating my time and money to it 🙂 , I am one of those people who has to cover every angle and make sure the plugin is up to the tasks i need. I often think that some developers who make plugins have great ideas but don’t always have the thought process to cover all of the angles and scenarios a user may or may not come across, i know a dev cannot cover all angles! …but i do believe with a bit of extra thinking like this first could save them alot of headaches down the line, im not referring to you by the way 🙂 i am just giving an example that most plugin devs concentrate so intensely on finishing their plugins and getting them released that they dont take the extra time to sit back and think about scenarios various users may face, this is true of most plugins released.
This is why i ask all these questions first because if i decide a plugin is worth the money i will buy it 🙂
I appreciate you getting back to me on this and thankyou for your time 🙂
This is a great idea but how would this apply to buddypress internal pages based on the users id? example: on the users profile pages and groups etc? how would you include these URIs?
ZenCache does not cache Dashboard administrative pages. It only caches the front-end pages on the site.
The Pro version already includes a URI Exclusion Patterns feature (please see the Pro Preview inside the free version of ZenCache) that allows you to exclude certain URIs from being cached and you can use a * to match any character. So if you wanted to exclude all profile pages and the profile URLs looked something like /profile/[username]/, you could simply exclude /profile/* inside ZenCache and all profile pages would not be cached.
ZenCache is very intelligent about which pages should be cached and which pages should not be cached and it automatically detects when changes occur on the WordPress back-end (such as saving a post, or changing WordPress settings) and automatically clears the appropriate cache files to ensure the site stays up-to-date.
I suggest you download ZenCache and give it a try.
If you’re looking for ZenCache reviews, keep in mind that this plugin was previously called Quick Cache, and has been around for more than 5 years and has been downloaded over a million times. 🙂
ty for your response once again, yes i will defo check the plugin out when i know it can get around the widget issues, but until then there is no point in even testing it really due to the concerns i raised above about the widgets updating, my widgets are set to auto refresh in 1 minute intervals but it seems until zencache can either exclude widgets on a per widget basis or it can somehow intelligently cache widgets that need updating frequently i will have to give it a miss.
The way my widgets are setup is one of the main features of the whole website and controls how users interact throughout my website, so to install a plugin that isnt yet ready to tackle how certain widgets need updating frequently would be pointless? because if i install zencache it will stop my widgets from updating thus rendering the website useless for what it aims to do!
ty for your help though and i look forward to your updates that can get around this problem for users of your plugin, please bear in mind more and more websites rely on heavy user activity and memberships day by day that involve using features i have integrated such as updating widgets frequently and will never be able to fully utilize the greatness of caching plugins because no caching plugin seems to deal with these kind of problems, ok its great that things like buddypress can now be cached with all the live updates that happen but if the users interact via sidebar widgets to let them see whats going on in other parts of the website its kind of pointless, cheers again.