Hello Stephane,

Can you provide us your backend and FTP access so we can have a better look on your issue here?

Don't publish my answer please.

Hi Stephane,

I am sorry, I can't login to your site. Can you please provide us with the correct access so that we can further inspect your site.
Warning
Username and password do not match or you do not have an account yet.

Please advise.

Here

Hello Stephane,

I am sorry for the delay of this reply.

After some long debugging on your site, it seems like your template 'Purity_III' is causing the token issue on your site. http://screen.stackideas.com/2015-03-09_1918.png
After I change the template into 'protostar' the invalid token issue is no longer appear. Perhaps you might need to consult with the template provider as well with your webhosting service provider in case they enabled super cache for your site.

Hope these help

Hi, thanks for your replie.
You know i change all my template and menu. I try and this is fix.
But when i added a link in my menu the same error appear.

In frontend for my blogger i have the same error. "not autorized to connect"
In Backend with the account of my blogger i cannot go to the composant easyblog.
I check all in the composant with my account, but i cannot see where is the problem.

Could you fix this please ?

Hello Stephane,

I am sorry for the delay of this reply.

I've set the ACL setting for your blogger account to be able to navigate easyblog component at your backend. He can now write a post, publish and monitor the blog. However something is really odd about your site. I am able to logged in into your frontend area but after I refresh the page or trying to navigate to other menu, I will get automatically logged out from the site. I also tried to disable suspicious plugin from your site but the issue still persist.

I even tried to disabled easyblog component completely and try to login into your site with new user that I created from the backend and yet the issue still there whenever I refresh the page at your site. Perhaps you might need to consult with Joomla developers regarding on this issue as they know best about joomla structure. I am sorry for the inconvenience caused