CB Login module gives error

We have upgraded our website to Joomla 4.
Now the CB Login module reports an error when I logout and try to login with another user ID.
The "normal" Login module does not have this problem.

CB 2.8.0+build.2023.05.26.14.42.43.3634ccdb3
Joomla ‎4.3.2

Robert

Joomla's security token failed. Do you have any form of caching enabled? It usually happens due to the form being cached causing the token in the cache to not be valid. Does this only happen if you login, logout, then login again? or on every login?

Yes, we have caching enabled.
It already happens on the first login, even when I have cleared the local cache for the last hour or so.
But why does the CB login have problems and the normal Login not?
Right now I am using the normal login. Could that cause problems with CB?

Robert

Try disabling caching and see if your issue resolves. Joomla's login module maybe clearing some caches before rendering to avoid that issue. We do have cache clearing in CB, but it might not be working depending on what caching you're using. Are you using page caching or caching server side?

You shouldn't even be able to use the Joomla login module unless you unpublished CBs system plugin, which is what handles the cache invalidation so that might explain why it's not working. Yes, using Joomla login can be a problem as it bypasses CBs login approval and confirmation processes as well as doesn't fire CB login events. In a future CB release we will be discontinuing the login module in favor of just extending Joomla's login process though.

I did have the community builder system plugin enabled
For the caching we use JHC Optimize Pro. The built in cache from Joomla is disabled.
Maybe I will have to exclude the CB login module somehow (i don't know how to be honest)
For now I have solved this by doing the following:
- the normal login is shown with the access set to "guest"
- the CB login is shown with the access set to "registered"
That way the login works, but we will also show the image of the current user with a link to the profile.
It is not ideal, but it works.

Disable JCH Optimize Pro and see if your issue persists.