I know that's difficult to reproduce but I am sure, Its coming from Joomla.
Sure but it can also come from the 3party component. Here it sounds like a not closed session_start()
and it don't show the point where the first session_start()
is called and not closed.
Can you retest with current staging (3.4-dev)? As we have also file changes in this files so we can be sure that the issue still exists.
Category | ⇒ | Libraries |
Status | New | ⇒ | Information Required |
Yeah! Sure . I'll test it on staging site
Indeed sounds like a system plugin is starting a session before Joomla does. So make sure you have disabled all 3rd party (system) plugins when testing.
We haven't changed the sessions pretty much since 1.5. I did a refactor here #5088. But even that is unlikely to fix your issue - I suspect as has been mentioned a 3rd party service is intialising the session before Joomla. And you can only have one session open at a time so everything falls apart from there.
Labels |
Added:
?
|
I am closing this as an unconfirmed report at this time. It can always be re-opened if further information is provided that allows this to be replicated
Status | Information Required | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2015-01-20 19:44:06 |
Closed_By | ⇒ | brianteeman |
@aasimali i don't know how i can replicate this issue.
I would sugest to disable error reporting on a live site (should not show the message) and check if it is a Core or component (JomSocial?) issue. If it is a Core issue we need a way to replicate it with the core.