http://screencast.com/t/LMGEcUswAX4t

but problems

Can you login with the regular Joomla login or modules? Does it help if you clear your Joomla cache? I only ask as I have periodically seen this error over many years as well.

Jordan

Hello Jason,

These issues normally happens when you idle on the page for too long (exceeding the time defined in the session live time). You need to increase the session live time in your Global Configuration area.

Another reason for this is most likely because of caching. Did you turn on the "System - Cache" plugin?

sistem cache plugin is ON
Global System 20
unsolved problem

I get the invalid token issue every once in a while too. I admit that there are times I may leave my site open in a separate tab for a while.

Set the number to 300 for the session lifetime and see if the issue happens.

Yes, 20 minutes could be a little low if you are idling on the page. Also what sort of cache mechanism are you using for the site?

cache Joomla only

Hello Jason,

Are you able to reproduce this very often? If you are able to reproduce this very often, try to turn off the cache just to see if you hit similar problems?

The problem we have 600 registered users on my site.
And it's not the cache

Jason, set the "Session Lifetime" to a high number like 300. If it's a low number, the odds of this issue happening are much higher. The Session Lifetime is on the same config page as the cache option.

We know it's not the cache. (well, at least as far as we know). Please check the session lifetime which is different from the cache. This controls the time of the login session.

Yep, please try as Josh mentioned

Problem is not cache

I can't reproduce this issue on your site so I have no idea how to debug this

You must access the module through EasySocial Log Box in page Home

Hello Jason,

I cannot reproduce this error. I have tried to login from http://policiasnacionales.es/ and it works perfectly fine.

http://screencast.com/t/BDoUXKaKcfN

Follow psando all users, send me emails to tell me Mark

Try out this method: http://www.camcloud.com/blog/how-to-solve-invalid-token-error-with-joomla

How often does this happen? What browser are you using? Have you tried logging in with a different browser?

I should note the login form with the register button that says "Registra tu Cuenta Hoy →" does not work.

Always happens. Google Chrome. Yes. Button not found, why?

Registered members also have invalid token problem.

There are only problems in this module. Why? (Hilo on the button register your account today http://stackideas.com/forums/register-fast-main-page,-i-can-not-remove-it-before-was-not)

Hello Jason,

To be honest, I can't replicate this issue on your site. I have tested this on Firefox, Chrome and Safari. All the login works fine. Anyway I have disabled a plugin on the site (I am not sure if that helps). Can you try clearing your browser's cache and see if the problem still occurs again?

Hello Mark you are fantastic, The problem I think was that plugin

It only remains to fix the module to run "register your account today".

And remove white space, so the buttons are aligned module, as the previous version

Mark Are you the best of quipo

Hello Jason,

Aha, so it was that "System - Cache" plugin it seems. After reading through the codes of the plugin, the plugin is causing the browser the cache the contents locally on the browser and it's probably causing these "Invalid Tokens".

I have already fixed the "whitespace" issues and replied on your other forum post

Mark is fantastic you, let me away
Just a detail, the blue button the login module does not work

Can you please be more specific of your issue? There's so many blue buttons on the site Which blue button are you referring to here?

jajajaja, module login home page, "Register with today"

Ah, okay. Fixed

If you want to use a page cache plugin (unlike the global cache set in Joomla Global Config), then you will have problems with many dynamic components such as EasySocial. An example of this problem is, for example, if you request a reset in your user password and EasySocial returns "We have sent your password request", that message will actually be cached and shown to the next user who views that same page! You have two options to get around this (in my experience).

1. Disable the system cache plugin but leave global cache enabled. This will still cache many things though not then entire content of a single page

or

2. Use JotCache instead of the Joomla system cache plugin. This amazing component allows you have page cache-like functions but you can specify which components (like EasySocial) to exclude. You can find this here: http://extensions.joomla.org/extensions/core-enhancements/performance/cache/13155

I went with option #2.

Jordan

Thanks for sharing this Jordan

Thank's Jordan, I'll try

Hello Jasonargo,

Glad to hear your issue now resolved
Have a nice day

Hi Jordan... regarding JotCache...

Jordan Weinstein wrote:
2. Use JotCache instead of the Joomla system cache plugin. This amazing component allows you have page cache-like functions but you can specify which components (like EasySocial) to exclude. You can find this here: http://extensions.joomla.org/extensions/core-enhancements/performance/cache/13155

I went with option #2.

Jordan

I've just started using jotCache, but I am now getting the dreaded Invalid Token error. Basically, if I clear my browser cache, I can log in normally. If I log out, and try to log in again, bang, up comes Invalid Token. I also use Chameleon to effectively give me a splash page for guests. I've tried configuring jotCache to stop it caching the token. jotCache does give me a huge improvement on page loading speed and reduced system resources so don't really want to ditch it.

So how did you stop this using jotCache?

Dave

@Dave - Did you get EasySocial working with JotCache? I excluded Easysocial in JotCache Component but still getting the 'Invalid Token' error. So until we get a solution I have to disable JotCache plugin.

@Jorden - Can you share more details of the solution for how you manage to get EasySocial work with JotCache?

Regards

Hi,

If you are using JotCache, did you disable the Joomla System Cache plugin (not the cache setting in Global Configuration).

Jordan

Hello Jordan,

Hm, just wondering about this. Does this mean that if a site has Jotcache and system cache running concurrently, users would face invalid tokens? I have never used Jotcache and don't really know what it's all about

Hi Mark, is it possible for easysocial to intercept invalid tokens error and redirect users to ES dashboard?

Hi again Mark,

This is my understanding:

The Joomla System Cache plugin caches an entire page output (including content areas). This results in very fast page loads but is not practical for for dynamic sites. Disabling this but enabling the system configuration cache, allows one to cache Joomla modules but not content areas. However, as you know, you can exclude individual modules from caching.

JotCache is basically a replacement for the System Cache plugin (so it caches content areas, components etc) but allows one to exclude not only module positions, but individual components from caching as well.

So if one was having invalid token areas with a component, my suggestion would be these settings:

Global configuration cache - OFF (can experiment with it on as well)
Joomla System Cache plugin - OFF
JotCache plugin enabled

If invalid tokens persist, try excluding the login module position from caching within JotCache. If the login module is a popup that is not in a Joomla/template module position (such as the EasyDiscuss toolbar login) then try excluding the EasyDiscuss component from within the JotCache > Exclude URL options.

Jordan

Dave Parker wrote:

Hi Jordan... regarding JotCache...

Jordan Weinstein wrote:
2. Use JotCache instead of the Joomla system cache plugin. This amazing component allows you have page cache-like functions but you can specify which components (like EasySocial) to exclude. You can find this here: http://extensions.joomla.org/extensions/core-enhancements/performance/cache/13155

I went with option #2.

Jordan

I've just started using jotCache, but I am now getting the dreaded Invalid Token error. Basically, if I clear my browser cache, I can log in normally. If I log out, and try to log in again, bang, up comes Invalid Token. I also use Chameleon to effectively give me a splash page for guests. I've tried configuring jotCache to stop it caching the token. jotCache does give me a huge improvement on page loading speed and reduced system resources so don't really want to ditch it.

So how did you stop this using jotCache?

Dave

When you log out, do you remain on the same page where the logout took place or do you redirect, say, to the home page? If you have a redirection to a different page, it might solve the problem as a new token will be generated for the login module. Otherwise, see my other reply from today just above.

Hello Kabeer,

Unfortunately we cannot "intercept" invalid tokens because when that happens, Joomla already exits everything else.

@Jordon - thanks for replying with the details. I have tried it again based on what you have suggested but invalid token error do not go away. I believe its probably because I have all ES, EB and ED on my site. So at this time I have the following settings which are working:
1. System Cache Off
2. Global Config Cache On
3. Jotcache installed but Jotcache plugin turned Off.
4. JchOptimize Pro On

When I enable Jotcache plugin the site pages loads faster but invalid token error persists. So shall I leave JotCache or remove it since JotCache core Plugin is disabled (but other Jotcache plugins are On)?

@Mark - thanks for letting me know. At this time I am doing a trial and error testing with JotCache and will let you know the optimal settings that works with JotCache and all ES, EB and ED.

Kabeer

This plugin works very well:

http://extensions.joomla.org/extensions/access-a-security/site-access/login-redirect/23925

Used this for a while now (huge issues with Varnish & sessions, mostly fixed via custom vcl) to catch and redirect rare invalid token messages.

Matthew Pate wrote:

This plugin works very well:

http://extensions.joomla.org/extensions/access-a-security/site-access/login-redirect/23925

Used this for a while now (huge issues with Varnish & sessions, mostly fixed via custom vcl) to catch and redirect rare invalid token messages.

I tried this on a localhost and it did not work. Interesting idea though.

Kabeer Khan wrote:

@Jordon - thanks for replying with the details. I have tried it again based on what you have suggested but invalid token error do not go away. I believe its probably because I have all ES, EB and ED on my site. So at this time I have the following settings which are working:
1. System Cache Off
2. Global Config Cache On
3. Jotcache installed but Jotcache plugin turned Off.
4. JchOptimize Pro On

When I enable Jotcache plugin the site pages loads faster but invalid token error persists. So shall I leave JotCache or remove it since JotCache core Plugin is disabled (but other Jotcache plugins are On)?

@Mark - thanks for letting me know. At this time I am doing a trial and error testing with JotCache and will let you know the optimal settings that works with JotCache and all ES, EB and ED.

Kabeer

Are you logging in from a login module in a template position or using the Easy* toolbar login?

Hi All.
I finally seemed to solve my issues with JotCache. Whether it's specific to my site I don't know, but worth a try for you.
What I did was to exclude the "com_content" component from caching in JotCache. The moment I did this, no more "Invalid Tokens".
Give it a go.
Dave

Dave Parker wrote:

Hi All.
I finally seemed to solve my issues with JotCache. Whether it's specific to my site I don't know, but worth a try for you.
What I did was to exclude the "com_content" component from caching in JotCache. The moment I did this, no more "Invalid Tokens".
Give it a go.
Dave

That seems strange. Were you loading a login module using 'loadposition' within an article? Excluding com_content will obviously reduce some advantage of the plugin for those pages. But better than nothing.

Thanks for sharing this Dave