Recommend caching plugin for BP
How does it handle whitelisting pages like registration and activation pages
let me know what issues u found with registration and activation pages?
I can’t speak for all the BuddyPress development team but, personally, I would not recommend W3TC. There is a specific bug with its Object Caching implementation that breaks password resets on BuddyPress for some obscure reason we weren’t able to track down.
You need an Object Cache plugin, which will be backed by a Memcached or Redis instance, or something. If you’re using a great WordPress host rather than any old common host, like WP Engine or Pantheon or Siteground, they already have this infrastructure in place.
You could have a full-page cache, but be sure to only configure it to cache requests for logged-out users. You can imagine that if the majority of your traffic is from logged in, then having a cache for logged-out views isn’t going to have much impact.
Interesting….thanks for the inputs @djpaul ..I guess I never had any user doing reset password on my site as mostly login via their social accounts…
I got my own server got xcache installed at backend and use w3tc’s object cache option..
You hit the nail on the logged in users no caching..any suggestions to speed up site for logged in users?
Does js/CSS minify really help?
Sure does. But if you had 100 pictures on one page, that’d be the biggest cause of slowness for that particular page.
Use Chrome dev tools (the “Network” tab) to sample a few pages (home page, user profile, directory) and look at the size and see what’s happening.
Image caching would you suggest anything specific? W3tc’s db caching helps for the logged in users…not sure if that really helps or not
Very interested in this conversation. I have X cache enabled on my server. But deactivated w3tc when I started having issues with registration. Any tips can I set so that I know w3tc wouldn’t be interfering with registration. Is it as simple as turning of/disabling page caching.
Earl – If you want to use W3 Total Cache’s page cache, but want to whitelist the registration and activation pages, you should be able to do that within W3TC.
This is an old guide that I found on Google to show you how to whitelist pages in W3TC:
For your needs, whitelist the
/activate/page slugs or whatever you have those slugs set to in BuddyPress.
registration and activation pages should not be cached as its for logged out users i believe
So is this is definite “Object cache doesn’t work inside W3 Total Cache” because it breaks password resets? This seems to be my experience.. I’ve whitelisted registration, membership (Paid Memberships Pro) and activation pages in the page cache but seem to have issues with password reset and account activation since using activating xcache Object Cache within W3.
So my questions are:
1) is there a different object cache plugin I could use alongside w3 (which is great for its page cache etc)?
2) is this issue unique to xcache? Could I use APC instead?
3) are there any other integrated cache solutions that work with Buddypress that include object cache? The benefits to my site speed have been huge since activating.. It’s just the account activation issue
May be consider WP Rocket, a premium cache plugin: https://wp-rocket.me/features/
WP-Rocket seems to work fine for me so far, and includes a Logged-In caching feature. No complaints yet on https://aica-canada.org
I looked at WP rocket and they don’t list any object caching in there feature list so that would really solve the issue with not using W3 total cache. My host only allows memcache on dedicated server not VPS. So still trying to find alternative.
@earl_d what did you end up using? I’m in the same boat. Did you find an alternative, or figure out a way to get around the password reset and account activation issues and still use W3 Total Cache?
Edit: I am not experiencing the account activation issue – just tested that. I’m only having problems with the password reset when using W3 Total Cache and BuddyPress. If I deactivate W3 Total Cache, the password reset works just fine, so the caching plugin is obviously the problem.
For me, I am using HHVM+php5.6+nginx helper, and using object cache with Redis, and no page cache used.
after testing, I found the first one:redis-cache will cause 502 error if buddypress actives steams is enable in Musite by now, and hope the author of redis-cache can upgrade it soon.
and the second one of Wp-redis woring fine with buddypress now.
I read a lot article by Very senior wordpress developers do not recommend Page cache, but strongly recommemd Object cache, here is some for your referrance:
I did not test W3, just as what @Paul Gibbs said:
I would not recommend W3TC. There is a specific bug with its Object Caching implementation that breaks password resets on BuddyPress for some obscure reason we weren’t able to track down.
You need an Object Cache plugin, which will be backed by a Memcached or Redis instance, or something.
I spend almost more that 3 months to setup cache for buddypress, and finally I agree that Redis object cache is really great for buddypress, including Woocommerce, and actually, I think it would be much great and very helpful to us if there is an instruction of caching setup for buddypress under documentation directory at http://www.buddypress.org, since there are still cache rules need to setup.
and I hope Redis cache experts can share their experience buddypress Forum.
- You must be logged in to reply to this topic.