Support Forum

Hi i'm running PostNuke(0.762) on Windows Server 2003 with IIS 6 as webserver,
Today i updated PHP to version 5.2.0
After this update it is not longer possible to login to my site (either as admin or regular user)
Once i submit the login form i get the "you are being logged in" screen and then it resturns me back to the index, in my logs i got this error message:

Code

PHP Fatal error:  Call to a member function Execute() on a non-object in C:\Inetpub\postnuke\includes\pnSession.php on line 378.

Is the current PostNuke distibution incompatible with PHP 5.2.x and/or are you aware of any issues like this?

RvdH



edited by: Ruudje, Nov 03, 2006 - 08:20 PM

http://community.postnuke...wtopic-topic-50830.htm

-----
-- David Pahl -- (PostNuke Support Team)

<div id="me" class="none" style="none" />

same here. PN .763, PHP v5.2.0.. register_globals is off

Quote

Call to a member function on a non-object in pnSession.php on line 378

it's pretty bizarre.. seems to only affect pnSessionWrite();



edited by: InvalidResponse, Nov 03, 2006 - 11:57 PM

-----
http://www.invalidresponse.com

session_info table corrupt?

-----
Regards,
Simon

itbegins.co.uk - PostNuke Consulting

Please read the Support Guide

HammerHead

session_info table corrupt?

How can i check that? am i able to repair (& how)?

EDIT: After turning back to PHP 5.1.2 i don't have this problem, telling me it is PHP 5.2.x related



edited by: Ruudje, Nov 04, 2006 - 11:35 AM

I can reproduce this issue on my local test system too but haven't really had chance to look into it closely. It seems that by the time pnSessionWrite is executed the global database connection object no longer exists. As yet I can't explain why this is the case. However the .8x session code works fine.

At this stage i'd recommend people stick with PHP 5.1.x or the latest PHP 4.x builds.

-Mark

thx for your reply mark,
will stick with 5.1.x for the time being...

FYI -- this looks to be the problem:

http://bugs.php.net/bug.php?id=39381

found other topics around the net with similiar problems, seems they found a workaround
http://drupal.org/node/61900
http://drupal.org/node/92802




edited by: Ruudje, Nov 06, 2006 - 11:05 PM

Is there a chance for a similar simple workaround in PN? I have apache 2.2.2 installed and as far as I know PHP 5.1 won't run on it... So I would have to reinstall the server to go back to 5.1 :(

Not a workaround... well it is, but to your second delima, apacheaounge.com has a driver available to make apache2.2 work with PHP 5.1. and it worked fine for me. That is until I upgraded to PHP 5.2, which I'm now off to downgrade .

-----
viewTopiaryWorks($twWorks, $twRosterMaster)

Thanks for the tip, will try it out.

Seems that the best solution for the moment is a downgrade of all PHP 5.2 components to PHP 5.1, which works fine with Apache 2.2 and MySQL 5 WITHOUT any special driver. I would suggest to not upgrade to PHP 5.2 until fixes packages are available for your operating system. Specially libapache2-mod-php5 (version 5.2) will need a fix which will be ready soon.

There is however no reason at all to run PostNuke on less than that - outdated Apache1 or PHP4 do make any sense, except you still need them for other reasons.

Greetings,
Chris



edited by: slam, Nov 08, 2006 - 03:25 PM

-----
development is life. w3you.com
an operating system must operate. sidux.com

Hi:

Any update regarding this? Drupal have this discussion and a 'fix':
http://drupal.org/node/92802

I don't know if the PHP guys are working on it, but some reading of the bug seems like they are not... IMO.

Later

Hello,
Reading Ruudje post (see above in this thread), I have found a workaround for this problem.
I've migrated to PHP 5.2 and experienced the problem.
I modified includes/pnSession.php in order to add in function pnSessionSetup()

Code

register_shutdown_function('session_write_close');

just before

Code

session_set_save_handler('pnSessionOpen',
                             'pnSessionClose',
                             'pnSessionRead',
                             'pnSessionWrite',
                             'pnSessionDestroy',
                             'pnSessionGC');

My web site worked again after this fix. I can log in again now.
Hope this helps.
Fred