I have a site that is implemented in Joomla 3.1.5 on which the following are installed
http://www.joomlart.com/joomla/templates/ja-muzic --> This is the theme
http://www.jomsocial.com/ --> Used as the community plugin
http://www.kunena.org/ --> The forums plugin
http://getk2.org/blog --> The Blog plugin
Of course there are some custom components and modules that are implemented.
The issue i am facing is that there is some kind of conflict happening between the sessions i think. What happens is that the session times out randomly or i get a error message as "Invalid Token". All this even when the pages is being used continuously.
I have checked the value in the back-end config , Session Lifetime is set to 60 and Session Handler is set to Database
Let me know if you need more info.
Any help or direction would be appreciated.
Thanks
The problem is actually caused by JomSocial and the cache plugin. Try disabling caching or changing the order of the cache plugin.
Worst case scenario, you can disable the "Invalid Token" issue in the code - but that solution would be a bit extreme (but, if all else fails, it's the only solution).
PS: For an in-depth about the "Invalid Token" error, you can check here: http://www.itoctopus.com/invalid-token-on-joomla-login
Related
Using Wordpress 4.0.1 , activated multisite for bolgging.
no. of themes are loaded. But when trying to customize themes, the customize.php page not loaded.
Its getting 504: Gateway Timeout Error
Any one know about this?
SOLVED! I figured out what the problem was with. I'll post the solution here, in case anyone else runs into it:
It might be a compatibility issue with one of the plugins, so I deactivated all of them, then I logged out and logged back in. Then I systematically activated each one, one by one. After I activated one, I'd check the customize page to see if it was the one causing the issue. I found that the Network Latest Post plugin is the one causing it to hang up for me.
Hope that helps someone!
I'm using HWIOAuthBundle (with google configuration) for authentication in one of my project.
It works very well most of the time. But at some point when I surf on the application, I get an error about the google_id. It doesn't appear on a specific page but all sudenly (after a period of inactivity). Basically, the google_id that my user provider get is suddenly null. As I'm not able to reproduce the error and it's very difficult to debug.
It seems to come from either the HWIOAuth bundle for which I'm may be using wrong configuration settings or from Symfony 2 session. But I tried changing the session life time and nothing work (as I said I'm not beeing able to reproduce the error on demand. It appears out of the blue...).
Do you have any idea how to solve this issue?
Regards
I've encountered the same issue. The access token retrieved from Google is no longer valid and needs to be refreshed. Unfortunately I haven't found out a good way to do it.
I have been working on an elgg site but have found that whenever I log out, the session does not seem to be cleared and I am logged back in within a few seconds. I have to delete my browser history in order to stay logged out.
I have disabled the social login plugins that I am using yet still the same issue occurs.
Has anyone else experienced this and does anyone know how I can force Elgg to completely clear the user session on logout?
The problem was being caused by the 'profile_manager" plugin from ColdTrick. I narrowed it down by disabling plugins and then once I discovered the offending item, I tried changing its load position. By placing it at the very end of the plugins list, the issue was solved.
Thanks.
I'm trying to build a service proviuder (SP) site for a client using a SAML2.0 based user ID system.
I've been able to install simpleSAMLphp on my server and have tested it with an open IdP authentication network - all is working fine if I just create php files which demand authentication against this IdP. Simple adding this to any page makes it work.
require_once('../simplesamlphp/lib/_autoload.php');
$auth = new SimpleSAML_Auth_Simple('default-sp');
$auth->requireAuth();
$attributes = $auth->getAttributes();
Within CMSMS however, if I add the above as a user defined smarty tag (the usual way of including php) I get a "state lost" error. I've tried adding it to the page meta data (via the content interface) as well as simply in the body of the page or at the head of the template.
I always get:
State information lost
State information lost, and no way to restart the request
Does anyone have any ideas what could be going wrong? I've tried the usual fixes for this error messages (adjusting the domain the cookies are assigned to in php.ini etc). No joy.
This seems like conflicting session management between simpleSAMLphp and CMSMS.
A simple way around this is to install memcached, and use the memcache session handler instead of the php session handler in simplesamlphp.
http://simplesamlphp.org/docs/stable/simplesamlphp-maintenance#section_2_1
similar session conflict is also with eZ publish (4.x) and Symfony2 (2.3+). SQL session storage solves that problem
I have an Auth component (based on Zend_Auth) which I am using in many projects on different servers and different environments. It has always worked... until now:
When I try to log in to a new project (using the same Auth component) with Google Chrome (12.0.742.122), I'm being logged out right after logging in. The problem doesn't occur with FF or IE.
Does anyone have a clue why this could be?
This is not a ZF issue. As strange as it may sound, the issue is solved by adding a favicon to your site. Chrome is making a request for the favicon and invalidating the session when it gets a 404. I read one post that suggested that a special 404 configuration might help.
Might be this bug: http://framework.zend.com/issues/browse/ZF-11502 - there is a fix suggested in the comments.
It is a weird story. If you google the problem, you find that it sporadically turns up here and there but never systematically. There is a bug report for Zend Framework, there are issues at the Google Forums, there are similar reports in the tracking systems of Drupal and Wordpress. But somehow there are no clear answers.
In my case, the problem just went away by itself in the course of some other refactorings.
Just a hint ... I had the same problem. After debugging I found out there is a clash with cookie name on the main domain. It worked in FF and IE, Chrome however took a top domain cookie for ajax request and the lower one on regular request.