That is very strange. I would almost say it is something to do with the evobar because that is the only thing that changes when logged in or not on the public side, but let's test some stuff and see...

Can you change your skin to an unmodified version of either 'custom' or 'evopress' and see if the problem remains? That would rule out or prove the skin itself as a problem. Another test would be to create a brand new blog and select an unmodified version of 'custom' or 'evopress' to see if maybe a widget (possibly from a plugin?) is making the error happen when you are logged in.

inc/sessions/model/_session.class.php ( approx 159 ) Change it to look a tad like this :

						// Unserialize session data (using an own callback that should provide class definitions):
						//$old_callback = ini_set( 'unserialize_callback_func', 'session_unserialize_callback' );
						$old_callback = false;
						if( $old_callback === false || is_null($old_callback) /* disabled, reported with PHP 5.2.5 */ )
						{	// NULL if ini_set has been disabled for security reasons
							// Brutally load all classes that we might need:
 							session_unserialize_load_all_classes();
						}

¥

EdB wrote:

That is very strange. I would almost say it is something to do with the evobar because that is the only thing that changes when logged in or not on the public side, but let's test some stuff and see...

Can you change your skin to an unmodified version of either 'custom' or 'evopress' and see if the problem remains? That would rule out or prove the skin itself as a problem. Another test would be to create a brand new blog and select an unmodified version of 'custom' or 'evopress' to see if maybe a widget (possibly from a plugin?) is making the error happen when you are logged in.

hi EdB,

I have changed it to custom skin, but the problem still exist. I haven't tried making new blog, I will try it if I have free time. Thanks anyway.

hi ¥åßßå,

I don't know where to change those scripts, I am not good at php.