Tracking logouts - HELP!

Next topic

Author	Message
Simon Phillips	Monday 28 February 2005 12:52:44 am Hi folks, I've added in some custom triggers to detect logouts and logins in ezPublish (will be publishing the code soon). However, it appears that the session data is never restored when the logout page is loaded - so I can't identify which user is logging out. Try it for yourself! If I put code within the logoutCurrent method of the ezUser class (which is the method run by user/logout.php), the $user object that supposedly contains the current user prior to logout is just the anonymous user. Even if I drop code in logout.php (and all this is before the actual 'logout' code has been run), the current user object is simply not available. I can't work out why - it's as if the session loader isn't being called, or the session is being destroyed in a previous method call - but I'm having trouble following the code execution through from the inital call to index.php and working out where it's happening. And yes, I am logged in. And the logout does indeed log me out. <b>Please help!</b> I know that svn being hacked might be more exciting, but I'm getting desperate... Simon

Author

Message

Monday 28 February 2005 12:52:44 am

Hi folks,

I've added in some custom triggers to detect logouts and logins in ezPublish (will be publishing the code soon). However, it appears that the session data is never restored when the logout page is loaded - so I can't identify which user is logging out.

Try it for yourself! If I put code within the logoutCurrent method of the ezUser class (which is the method run by user/logout.php), the $user object that supposedly contains the current user prior to logout is just the anonymous user. Even if I drop code in logout.php (and all this is before the actual 'logout' code has been run), the current user object is simply not available.

I can't work out why - it's as if the session loader isn't being called, or the session is being destroyed in a previous method call - but I'm having trouble following the code execution through from the inital call to index.php and working out where it's happening. And yes, I am logged in. And the logout does indeed log me out.

<b>Please help!</b> I know that svn being hacked might be more exciting, but I'm getting desperate...

Simon

eZ debug

Timing:	Jan 18 2025 22:24:45
Script start
Timing:	Jan 18 2025 22:24:45
Module start 'layout'
Timing:	Jan 18 2025 22:24:45
Module start 'content'
Timing:	Jan 18 2025 22:24:45
Module end 'content'
Timing:	Jan 18 2025 22:24:45
Script end

Main resources:

Total runtime	0.0174 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0072	589.0234	152.6094
Module start 'layout'	0.0072	0.0032	741.6328	39.4141
Module start 'content'	0.0104	0.0053	781.0469	85.1172
Module end 'content'	0.0157	0.0017	866.1641	30.3047
Script end	0.0173		896.4688

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	13.7161	14	0.0002
Check MTime	0.0010	5.8983	14	0.0001
Mysql Total
Database connection	0.0010	6.0233	1	0.0010
Mysqli_queries	0.0031	17.8584	3	0.0010
Looping result	0.0000	0.1263	1	0.0000
Template Total	0.0013	7.7	1	0.0013
Template load	0.0006	3.6274	1	0.0006
Template processing	0.0007	4.0434	1	0.0007
Override
Cache load	0.0004	2.5098	1	0.0004
General
dbfile	0.0002	1.4018	8	0.0000
String conversion	0.0000	0.0590	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs