Menu

Notice: Undefined variable: post_user

Help
harwood31
2004-01-06
2004-01-16
  • harwood31

    harwood31 - 2004-01-06

    I'm migrating a postnuke website to a new server and new MYSQL database and had no troubles using the mysqldump tool to duplicate the databases until I tried the phpGedView module and got this:

    Notice: Undefined variable: post_user in C:\inetpub\aaa.com\modules\phpGedView\postgedview.php on line 65

    Notice: Undefined variable: post_user in C:\inetpub\aaa.com\modules\phpGedView\postgedview.php on line 68

    Notice: Undefined variable: post_user in C:\inetpub\aaa.com\modules\phpGedView\postgedview.php on line 92

    Notice: Undefined variable: post_user in C:\inetpub\aaa.com\modules\phpGedView\postgedview.php on line 94

    Notice: Undefined variable: post_user in C:\inetpub\aaa.com\modules\phpGedView\postgedview.php on line 105

    Warning: Cannot modify header information - headers already sent by (output started at C:\inetpub\aaa.com\modules\phpGedView\postgedview.php:65) in C:\inetpub\aaa.com\modules\phpGedView\postgedview.php on line 108

    I can open the index.php file directly and view the data intact, but my link on the website is broken.  I think the problem will lie somewhere in the postnuke/php build but I'm missing something somewhere.  The move entailed a simple file copy from one system to the next and changing file permissions.

    Any thoughts?

     
    • harwood31

      harwood31 - 2004-01-06

      BTW: the rest of the site appears to be working fine suggesting the php/mysql/pokenuke apps are installed and working correctly.   Since phpGedView is the only non-working module I think its something very specific which only its uses.

       
    • harwood31

      harwood31 - 2004-01-07

      Help?  I'm still suck.

       
    • John Finlay

      John Finlay - 2004-01-09

      I don't really use the PostNuke module, but since Jim isn't around, I'll try my best to help.

      The link into PhpGedView from PostNuke should look like this:
      http://carey.id.au/modules.php?op=modload&name=phpGedView&file=pgvindex

      Your entry point should be the pgvindex.php file where the post_user cookie is set and then passed onto the postgedview.php page.

      The pgvindex.php file is the file that bridges the postNuke settings over to PhpGedView.

      --John

       
    • harwood31

      harwood31 - 2004-01-09

      Thanks,

      I'll double check that line.  Essentially I'm trying to duplicate the site onto another several of similar configuration and in the process of copy the php site folder and an apparent successful MYSQL database copy (no errors anyway and postnuke security/logons appares to work normally) I assuming that the path to the pgvindex file hasn't changed.  I should add that I've also tweaked the 'DEV Server" to only point to the localhost as my site, so DNS aside everything should be running locally to the new server.

      However, there is one major differnece I'll investigate.  The system now has two volumes, one system, and another where the website folder is located and I bet the cookie file is on the other volume which is at another file path....  Does the cookie reference a direct windows file path??  If so I might have to re-do my server's HD configuration....

       
    • John Finlay

      John Finlay - 2004-01-09

      The cookie is domain specific not path specific, so it you are switching domains the path with be lost.

      --John

       
      • Jim Carey

        Jim Carey - 2004-01-09

        sorry - was on a long booked holiday to the UK and didnt check emails. Arrived back in OZ yesterday and slept :-) Jet lag means it's 5 am and I am bright as a button !

        let me know if John's reply didn't sort the problem - should have if all your files were up in a dir called phpGedView in the postnuke modules dir. The system is quite simplistic so any probs should be relatively easy to solve :-)

        cheers

        Jim

         
    • harwood31

      harwood31 - 2004-01-09

      Thx a bunch for the tips, I''l check and re-check this tonight.

       
    • harwood31

      harwood31 - 2004-01-16

      eureaka!

      This was being caused by a missing file permission.  The Index folder needs Write permission for the webuser.  Changed that and now it works again.

       

Log in to post a comment.