Hi Brajesh (Happy Diwali!) and Carsten,

I also use Litespeed cache and I’ve been thinking that a recent Litespeed update might be the reason that my Member Types checkboxes in the Xprofile Field don’t persist. Brajesh and I have been discussing this and he thought it related to caching. My users have to log out and back in for their saved data to be shown correctly. Try that, change a setting in the profile and then log out and back in, see if the setting has been saved.

In the toolbar menu, Litespeed option, caching can be turned off for individual pages. I’m thinking of turning it off in the Profiles. I haven’t wanted to do that yet until I have sufficient time to be rigorous about testing. Because my site is a Multisite I have to take a lot of care over setting the Litespeed cookies correctly per sub-site, so testing is not quick. I only have very basic Litespeed caching in place at the moment, nothing fancy.

However, I think Brajesh is correct and I think we will have to do some experiments with Litespeed settings. There are a lot of settings as you’ll know!

I’ll monitor this thread and join in if I have any useful results to share.

Best wishes,
Mike

Hi Mike,
Happy Diwali 🙂
Thank you for the help here.

Hi Carsten,
The issue is not related to us. AS it is due to new update of the caching plugin, Please contact their support.

Regards
Brajesh

Both,

Adding this for people who are not familiar with Litespeed. If set up correctly, Litespeed caches pages, objects, widgets etc for individually logged-in users directly on the server’s disk (which will undoubtedly be an SSD). It is one of its best features and makes it the fastest cache around in my opinion. Simplistically, you have to specifically buy hosting with Litespeed’s system because it replaces the Apache system.

For now I’m using the following to exclude some sections from the Litespeed cache.

In the Litespeed plugin > Settings > [4] Excludes > Do not cache URLs

members/
members/*
forum/
forum/*
activity/
activity/*

When you enter these every letter you type is delayed because Litespeed is detecting what you type. Be patient.

‘members’ are the two slugs you need in particular because that will exclude the users profiles.

Litespeed will then cache the logged-in member individually except when they (or visitors) are visiting a subset of those slugs. This is better than not caching your logged-in users everywhere.

Of course, you have to have the Litespeed cookie set up for your WordPress installation for Litespeed to know who is logged in or not. However, the method above will exclude the slug and its children from caching whether the cookie is set correctly or not. therefore, it is a ‘simple’ method.

An alternative is to start to focus-in on the logged-in user and refresh parts of their cache on a short interval. However, if you do that there will always be a delay for a user changing a profile setting. I think that even a delay of a minute would be confusing for the user, you would have to set up a cron to run every minute and they would have to wait a minute to see the results.

I hope that helps for now and I’ll report back if I get further with it.

Best wishes,
Mike

• This reply was modified 5 years, 1 month ago by Mike (DesignServe). Reason: Corrected one of the slugs and added more explanation

PPS moreover, you could just use members/* and then your members directory (members/) will continue to be cached.