this appears to be caused by the litespeed cache component, disabling the cache fixes the problem

Hi Greg,

Thanks for the update. May I know if the issue here still persists after you disabling the cache component above?

No the problem does not seem to persist when disabling the litespeed cache.

You can recreate the issue by logging into the administrator control panel and navigating to
administrator -> components -> litespeed cache -> options -> basic -> enabled

whats weird is that it only seems to affect the easysocial form.token and not the joomla form.token

Hi Greg,

Ah, I see. Most likely it is because of this exclusion setting in LiteSpeed cache options that causing to work fine in Joomla user login, https://take.ms/1FTAc. Regardless, glad to hear that issue has been resolved now.

I added that exclusion to test if it helped... it didnt

Thanks for the update, Greg. Unfortunately, there is nothing that we can do to help here . It is best if you can consult directly with LiteSpeed developer and see what is the best approach that they can offer in order to help fix this issue.

I will lock and mark this thread as resolved for now to avoid confusions in the future. Please start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiries.

Thanks for understanding.