By HMED on Monday, 26 October 2015
Posted in General
Likes 0
Views 2.2K
Votes 0
Hello,

i get this message some times when i check the home page wich is the ES dashboard,
its dispear when i refresh with ctrl+F5

 Notice: A session had already been started - ignoring session_start() in /srv/users/serverpilot/apps/public/libraries/joomla/session/session.php on line 665
Hey Jan,

I am sorry for the delay of this reply,

I've tried to login several times in your site, but I can't reproduce this error.

By the way, based on the error message, it actually detect the current login user session still exist so it show out this notice message, I believe that was your site cache issue.

To test this, you can temporary disable your site cache then re-test again.

If the error still persist, perhaps you can set your error reporting to NONE, or open this file JoomlaFolder\libraries\joomla\session\session.php

// LINE 665
session_start();

// Replace with
if(!isset($_SESSION))
{
session_start();
}



Reference link : http://stackoverflow.com/questions/10648984/php-sessions-that-have-already-been-started

Hope this will help.
·
Monday, 26 October 2015 11:44
·
0 Likes
·
0 Votes
·
0 Comments
·
Thank you Arlex,
i disabled cache (option and system plugin) and the error dispear, its a cache problem, its due to my server configuration or joomla it self ?

error reporting is already set to none, strange that it continue showing errors !!
i will replace line 665, i found in the same topic this code, can use it ?

    if(!isset($_SESSION)) 
{
session_start();
}
else
{
session_destroy();
session_start();
}
·
Monday, 26 October 2015 19:17
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Jan,

I believe it's the way your current cache method is causing these errors but unfortunately this is beyond the scope of our support
·
Monday, 26 October 2015 21:32
·
0 Likes
·
0 Votes
·
0 Comments
·
Thank you Mark, the first code replacement seems working
·
Tuesday, 27 October 2015 01:47
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for updating, glad that your issues are resolved now but please do consider that these are issues that are beyond the scope of our support.
·
Tuesday, 27 October 2015 01:52
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post