Merged Invalid Token

I have been getting an "invalid token" error with Chrome.

I have the following installed:
Joomla:1.5.22
Jomsocial: 2.0.4
Kunena: 1.6.2

Sequence to reproduce error:
1. Log in using front end (joomla)
2. Click "remember me" box
3. Go to my Kunena forum
4. Read a post
5. Shut down Chrome
6. Open Chrome back up
7. Log back into front end of site.
8. Invalid token appears.

Anyone know how to resolve this error?

Do you experience these symptoms here, at www.kunena.org ? Have you searched the forum for "invalid token"?

I cannot duplicate it on here, and yes I have searched the forums, but did not see any solutions.

Go to your Joomla Global Configuration page. Go to the System tab; what are the Session Settings?

Session=45 minutes
Session handler=database

Make session lifetime the same as Kunena session lifetime and turn session handler = none to see if this makes a difference.

I set kunena session to 2700 (=to 45 jooomla). Set handler to "none". That caused "invalid token" on original login. (step #1 above)

I suggest that you may need to ask your question at the Joomla support forum ( forum.joomla.org ) "Invalid token" is a Joomla issue. It's not really a Kunena issue.

Hi
I just had this exact problem - in fact I've had it before. I appreciate this is an old topic, but posting here in-case others find the same. Also this is a Joomla! issue, not Kunena - I'm sure of that.

Invalid tokens have been caused for me because of having the system-cache plugin enabled. This caches whole pages including the login modules, both in Kunena and other pages on the site. effectively it can end up looking like you are logged out - because you are seeing a cached page.

My setup has cache enabled in the site-global configuration, but the system cache plugin, must be disabled or I get all sorts of problems.



What I can't work out is how that system cache keeps getting turned on!

Hope this helps someone one day.

Rob

I fixed the invalid token by turning off sef all together. Its working so far, so looking for a solution so I can have sef in our website.