Session expired after enabling cache

I have recently enabled the system cache plugin in Joomla to avoid server overloading problems. I also enabled the Global cache and set it to conservative. Since I have enabled these two features, occasionally new members who are registering will get the message "Session expired or cookies not enabled..." after they have filled in all of their information and then click the register button.

I just now disabled the Global cache to see if that makes a difference. However, I am still asking the question because it takes a while for a response and this issue is time sensitive. This is the busiest time of the year for this website and new sign ups. Therefore I cannot disable caching because of the load on the server, but I cannot have new members not be able to sign up. I need a solution to this issue.

I notice that in other modules under advanced options there is a way to disable caching of that module. Is there a way to disable caching for CBSubs or CB in general? Shouldn't this be disabled for new registrations and logins by default? Do you have a recommendation for a plugin that I can use to have caching but ignore the CBSubs pages? What would I actually tell it to ignore?

Those extra questions are in case the first questions do not provide a solution.

Thanks!

You can disable spoof checking within CB > Configuration > Integration and this should get rid of the issue. The reason caching negatively impacts spoof checking is a unique code is generated and added to the post to validate the post. The code is attached to the users session. This prevents post spoofing. However, enabling cache causes old spoof values to cache resulting in a mismatch.

I have disabled spoof checking and the problem persists. Any other ideas?

Disable caching or try using a really short cache time (e.g. 5 minutes). It's caching the spoof checking which is added to the registration form html and that's causing the check to fail as it no longer matches database.

I cannot disable the caching (see first post) and making it a 5 minute cache seems like it would almost negate the benefit of caching.

If I have disabled spoof checking, how can that still be the issue? How can I tell if it is spoof checking?

I am running cb 1.9 and subs 3.0.0. Could there be a bug in my version that is causing this? I ask because I can't be the only person running this software on a large website with caching enabled. I really need a solution.

There's 2 forms of spoof checking. That parameter only shuts off one. The other is an anti-spam check to avoid registration being spammed from outsides sources. This one can't be disabled as it's vital for security.

Caching typically does not work in dynamic environments and caching should be implemented on a usage by usage basis. For example you wouldn't want to cache any of CB as its data is constantly changing. If global caching is used it needs to be short a duration like 5 minutes or you'll end up with users viewing an old registration form that is no longer valid. The security checks are just doing what they're designed to do; protect your site from abuse.