818 pointsLike some sort of WPMU DEV God"Mindblowingly helpful member
nickd32
Member
—
18th September 2011
Starting a new thread for this issue specifically. (Migrating from this thread)
Many WPMU users have turned to the Quick Cache plugin for its built-in multisite features. I've noticed a problem however with the "Clear Cache Manually (this blog only)" button that it installs in the upper right of the WP dashboard.
Let's say I have a Multisite network on MySites.com with a sub-blog called blog1.MySites.com, which is mapped to blog1.com
If you click the "clear cache" button while on blog1.com/wp-admin/ the cache clears just fine. . .
BUT, if you happen to be on blog1.MySites.com/wp-admin/, it doesn't clear the cache.
This is frustrating for users who aren't able to see their changes and can't figure out why the cache isn't clearing when they click the button.
Starting a new thread for this issue specifically. (Migrating from this thread)
Many WPMU users have turned to the Quick Cache plugin for its built-in multisite features. I've noticed a problem however with the "Clear Cache Manually (this blog only)" button that it installs in the upper right of the WP dashboard.
Let's say I have a Multisite network on MySites.com with a sub-blog called blog1.MySites.com, which is mapped to blog1.com
If you click the "clear cache" button while on blog1.com/wp-admin/ the cache clears just fine. . .
BUT, if you happen to be on blog1.MySites.com/wp-admin/, it doesn't clear the cache.
This is frustrating for users who aren't able to see their changes and can't figure out why the cache isn't clearing when they click the button.
Yes, we've noticed this too and contacted the plugin developer about it. It seems that caches are created by domain, not blog ID. For now, we have the domain mapping plugin set to log the user in at whatever domain they entered. So, if they use the mapped domain, the cache should work fine. But they won't be able to log in securely. If they use the original domain, they can log in securely via our wildcard SSL certificate. But the "Clear Cache" button won't work. However, the cache will clear at the preset interval.
It's not a perfect situation, of course. We're hoping that the plugin developer can figure out a solution. A while back he indicated that it would probably be possible to resolve it
They're logging in to their full account, but if they try to change to one of their other sites, they'll have to log in again. The login cookie doesn't transfer across domains.
However, the cache will clear at the preset interval.
What do you set that interval at?
I spoke to my hosting guy, and he said I could set it as low as 5 minutes (300 sec). I know the default for the plugin is 1 hour... but in the interest of NOT having users freaking out that "their content isn't updating when they refresh," I like the shorter interval.
The other option I can see is the Dynamic Cache Pruning setting. I could get away with a longer cache expiration (like 24 hours) -if- I set the pruning to to completely reset ( purge all cache files ) on ALL actions — like renaming a category or adding links.
Thoughts on (1) shorter expiration time VS. (2) pruning set to "all" ?
We haven't gone live yet, so we're still at the default and trying to decide what to set it at. Of course, the lower the setting, the more server resource usage (CPU, etc.), which probably isn't much of an issue on a beefy server.
One other thing I don't like about a lower setting: Of course, performance is better when a user visits a site with cached content. So, the more often the cache is cleared, the more often users will hit an uncached site and not get the benefit of caching.
Thoughts on (1) shorter expiration time VS. (2) pruning set to "all" ?
As I understand it, this will flush everyone's cache when one of those events occurs, right? I like that, however it also has the same issues as a shorter reset time in terms of resource usage and increasing the number of times that users hit uncached sites.
For that reason, we had not done the more aggressive dynamic pruning settings. But we are still evaluating.
Sorry I didn't have a more definitive answer. I'll let you know when we finalize our decisions, in case that helps.
We've been working on a new version of this plugin for awhile. It's pretty smart, but it seems to keep getting delayed for release due to various things. I'm gonna ask the developer where we're at on this one and see if we can get you all an update shortly.
I think Mason was a bit confused, the problem is with the quick cache plugin, not Domain Mapping.
I'm not familiar with quick cache, but I personally use wp super cache with caching off for logged in users or those who have left comments. I've never had a user notice pages not being updated in that case.
Is there any info that can be shared regarding solving this issue... I think this is the issue I'm having trying to login with ajax while domain mapping and quick quick are enabled.
Responses (17)
Member — 18th September 2011 #
One solution would be to change the Domain Mapping settings so that the domain used for the administration area should be the "mapped domain"
However, that's not a great solution, because it forces users to login to each of their sites separately.
I would rather leave this set to: "domain entered by the user"
Member — 18th September 2011 #
Also posted this question on the Quick Cache forums:
http://www.primothemes.com/forums/viewtopic.php?f=5&t=15191
Lifetime member! — 18th September 2011 #
Yes, we've noticed this too and contacted the plugin developer about it. It seems that caches are created by domain, not blog ID. For now, we have the domain mapping plugin set to log the user in at whatever domain they entered. So, if they use the mapped domain, the cache should work fine. But they won't be able to log in securely. If they use the original domain, they can log in securely via our wildcard SSL certificate. But the "Clear Cache" button won't work. However, the cache will clear at the preset interval.
It's not a perfect situation, of course. We're hoping that the plugin developer can figure out a solution. A while back he indicated that it would probably be possible to resolve it
Lifetime member! — 18th September 2011 #
I hadn't realized this. So in this case, users aren't actually logging into their full account where they can see all their sites?
Member — 18th September 2011 #
They're logging in to their full account, but if they try to change to one of their other sites, they'll have to log in again. The login cookie doesn't transfer across domains.
Member — 18th September 2011 #
What do you set that interval at?
I spoke to my hosting guy, and he said I could set it as low as 5 minutes (300 sec). I know the default for the plugin is 1 hour... but in the interest of NOT having users freaking out that "their content isn't updating when they refresh," I like the shorter interval.
The other option I can see is the Dynamic Cache Pruning setting. I could get away with a longer cache expiration (like 24 hours) -if- I set the pruning to to completely reset ( purge all cache files ) on ALL actions — like renaming a category or adding links.
Thoughts on (1) shorter expiration time VS. (2) pruning set to "all" ?
Lifetime member! — 18th September 2011 #
We haven't gone live yet, so we're still at the default and trying to decide what to set it at. Of course, the lower the setting, the more server resource usage (CPU, etc.), which probably isn't much of an issue on a beefy server.
One other thing I don't like about a lower setting: Of course, performance is better when a user visits a site with cached content. So, the more often the cache is cleared, the more often users will hit an uncached site and not get the benefit of caching.
As I understand it, this will flush everyone's cache when one of those events occurs, right? I like that, however it also has the same issues as a shorter reset time in terms of resource usage and increasing the number of times that users hit uncached sites.
For that reason, we had not done the more aggressive dynamic pruning settings. But we are still evaluating.
Sorry I didn't have a more definitive answer. I'll let you know when we finalize our decisions, in case that helps.
We have also pinged the plugin developer again.
Sales & Support Pro — 19th September 2011 #
Hi guys,
I'll ask the developer if he can update on where he's at with this particular issue regarding domain vs blog ID.
Phil
Lifetime member! — 21st September 2011 #
I've just heard back from the Quick Cache developer, and I'll be helping him test code in hopes of working on a resolution.
Member — 22nd September 2011 #
I've also tested his patch, with no success. Updates here:
http://www.primothemes.com/forums/viewtopic.php?f=5&t=15191
Lifetime member! — 22nd September 2011 #
Same here. I reported my experiences directly to the author, and I assume he's working on an updated patch.
Member — 6th October 2011 #
Looking forward to hearing more on this topic. Looking for an easy and reliable caching solutions
Lifetime member! — 6th October 2011 #
I haven't heard anything else since the first development version didn't work. I've asked the developer for an update.
Sales & Support Lead — 17th October 2011 #
Hiya guys,
We've been working on a new version of this plugin for awhile. It's pretty smart, but it seems to keep getting delayed for release due to various things. I'm gonna ask the developer where we're at on this one and see if we can get you all an update shortly.
Thanks!
Lead Developer — 17th October 2011 #
I think Mason was a bit confused, the problem is with the quick cache plugin, not Domain Mapping.
I'm not familiar with quick cache, but I personally use wp super cache with caching off for logged in users or those who have left comments. I've never had a user notice pages not being updated in that case.
Sales & Support Lead — 17th October 2011 #
lol! My bad. Musta been some other guy using my login credentials again... :P
Apologies for gumming up the thread!
Member — 31st December 2011 #
Is there any info that can be shared regarding solving this issue... I think this is the issue I'm having trying to login with ajax while domain mapping and quick quick are enabled.
Become a member