Some little additions:

When I try to log-in on my website (frontend) after I cleaned all cache in the backend, I am not redirected. There is no change on the page at all.
I need to reload the page ... and then it shows me the "logged view".

I could imagine, that this is some Ajax-stuff happening, so the login does work in that case, but the whole page is not reloadet.
This happens no matter if I take the "frontpage-login" or the "module-login" of easysocial.

All the best, Julian!

Hello Julian,

I am really sorry for the delay of this reply as it is a weekend for us here. Firstly what I would suggest you is to turn off every single caching plugin and disable the caching in Joomla altogether.

If you have already done the above, check with your hosting provider if there are any caching done on the webserver's layer. There's definitely some cache somewhere that is causing these tokens to not be renewed.

Hi Mark,

no need to be sorry ... I didn´t act on this issue for weeks, because it only was tiny feedback from my users.
I just realized slowly that this problems are very permanent and way too much.

What you suggest is all done:
I turned off every caching, I uninstalled stuff like JotCache and I disabled every plugin that has got to do anything with cache.
One more example for that behavior, that I could repeat easily:
When I sign in on my page (frontpage), the whole page is not reloadet. It stays as it is. Only when I reload the page manualy, the page reloads and the signed-in-stuff shows up (messages, welcome-message,...). Same when I log out: The "logged in" page stays until I manually reload the page.

About the hosting:
There is no caching that interrupts anything.
I have many other Joomla-Pages on the same server, they don´t have this issue.

So ... while I am sure, something is messed up in this joomla-installation and I guess (!) that Easysocial has something to do with it ... would it be possible that one of your technichans could check what it is? I don´t ask for it for free ... I am totally willing to pay for it, expecially because I don´t know if it is caused by EasySocial. But I can imagine, because most of the issues happen with EasySocial that it might be a good chance that we can find out the reason by looking at EasySocial. And maybe ... it could be caused by EasySocial.

There is one more thing that I remember:
The Installer does not work anymore since a while. I have to install new versions manually all the time.
Maybe this also is connected to this issue ...

All the best, Julian!

Hello Julian,

Can you provide us with your Joomla backend and FTP access so we can help you check on this?

Please ensure that disable all your possibility cache system from your site and server first.

Hi Arlex,

all is providet. And many thanks for the help!

Some information for you:

- I disabled ALL caching and all cache-plugins. It seems like in all AJAX-Stuff pages are not refreshed when they should. When I use the EasySocial-Login (upper right corner), nothing happens. I have to hit "reload" and then the page for the logged user shows up. But certainly only when I cleared the cache before ... else the security-token-message shows up.

- I also have the behaviour in Kunena: When I write a new posting, it is not shown. I have do a reload of the page (Shift-Reload), so the page with the new posting is shown. I have no Idea, why this happens.

- Today I switched the php-version from 5.5.13 to 5.3.28. So if you check anything about the php-settings, please keep in mind that it was switched recently!

- There are some subfolders where I have some other stuff in. But I think, they don´t matter for you.

- Please take care about all changes as it is a live-system and some (small) things are adjusted in the files. Nothing about caching.

- If you see any plugins that should be deactivated or that you think are not neccecary, just give me a note. In most cases, for example with stuff like jQuery, I don´t know what I can disable.

Thank you very much!

All the best, Julian!

Wait a moment: I MIGHT have it!!!

It is always the same structure: I got mad at something, and a few minutes after posting for help, I find something.
As I switched from JomSocial, I uninstalled all JomSocial-Extensions. But there was one plugin left, that was not named "JomSocial" but it was the "Azrul System Mambot", which had the explanation that it is for the JomSocial-Ajax-System.

My first impression after uninstalling that extension is: It might work!
So for the moment there is no need for you to fix anything on my website. I will check it and let you know, if all works fine now.

But however, do you have any experiance with the "Azrul System Mambot"? Do you know if this mambot causes problems?

All the best, Julian!

And once again ... sorry for posting such a lot, but I am soooo happy that this issue seems to be solved.

In the moment I am starting to believe that the "Azrul System Mambot" was causing all of that trouble. It mixed up all Ajax-Stuff and now, after deleting it, even when I turn on the cache, in my case JotCache, all works and I don´t get the security-token message anymore. In addition to that, all Ajax-stuff works as it should.
Sure, I will have to test some more, but in the moment ... all looks good.

However, it might (!) be a good Idea to put a check in your installation-routine. As you offer the migration from JomSocial and many of your customers will migrate from JomSocial, there is a good chance that other users run into the same problem. I know from the JotCache-Forums that there are other users also having the issues with login and security-token. Not neccecarily with EasySocial, but it´s a common problem.

If you simply add a little warning-message to EasySocial, if the Mambot is installed and active, this could possibly solve lots of errors for some users and it would not even appear on the screen for users who haven´t this Mambot installed.

So I will continue testing now and keep you informed, okay?

All the best, Julian!

Thanks for the heads up on this Julian but I think it's not a wise move to place such checks as this is like saying "JomSocial is crap, please remove it from your site" and it doesn't create a healthy competition at all

Hi Marc,

JomSocial is crap, please remove it from your site

Are you trying mind-reading?
This is NOT what I suggested. You can for example place a message like:

We found the JS-plugin Azrul System Mambot on your plugin-list.
This plugin may interfer with our AJAX-System, so if you face any messy
behaviour try to disable Azrul System Mambot and check, if the behaviour changes.

Nothing crappy about it, but a very usefull information.

All the best, Julian!

I thought of a fair compromise, instead it could say "EasySocial is not compatible with (extension name)" so that it doesn't talk down the extension and still informs the user. Just an idea if we go this route.

Thanks for sharing this guys We'll see what we can do about this but I really don't think their plugin is messing with our ajax calls (Not in the older versions that I know of). The only issue is that this plugin is most likely interfering with any caching / compressions script that you have.