Menu

2.51a release error

Help
2003-09-24
2003-09-26
  • Steve Lowmaster

    Steve Lowmaster - 2003-09-24

    John

    I just set up the 2.51a on the server. I set authenicate, config and ./index to 777

    The setup page comes up fine and takes the settings. The admin user seems to set up fine but when you the next page loads I get the following error messeges.

    Notice: unserialize(): Error at offset 0 of 5 bytes in /home/stevel/public_html/phpGedView/authentication_mysql.php on line 240

    Notice: unserialize(): Error at offset 0 of 2 bytes in /home/stevel/public_html/phpGedView/authentication_mysql.php on line 241

    Notice: unserialize(): Error at offset 0 of 1 bytes in /home/stevel/public_html/phpGedView/authentication_mysql.php on line 245

    Warning: Cannot modify header information - headers already sent by (output started at /home/stevel/public_html/phpGedView/authentication_mysql.php:240) in /home/stevel/public_html/phpGedView/login.php on line 41

    I'm not sure how to work with the unserialize() error so I'll hold off working with this one till I hear from you.

    Thanks Steve

     
    • John Finlay

      John Finlay - 2003-09-24

      Steve,

      Dropping your pgv_users table and recreating the admin user should fix this.

      --John

       
    • Steve Lowmaster

      Steve Lowmaster - 2003-09-25

      That did the trick.

      This might be a good thing to add to the readme text. If the program just dropped the user table and rebuilt it some people might lose all their users and not realize it until someone reported that they couldn't log in.

      I'm now getting an error since I changed the living individuals to user.

      Warning: Cannot modify header information - headers already sent by (output started at /home/stevel/public_html/phpGedView/privacy.php:307) in /home/stevel/public_html/phpGedView/functions.php on line 637

      The live site is offline right now but you can look at it at http://www.lowmasterober.com/phpGedView/

      keep up the great work!

      Steve

       
    • John Finlay

      John Finlay - 2003-09-26

      If you edit the privacy.php file and remove the empty line at the end of the file it should fix that error.

      PHP used to ignore the whitespace at the end of files.  I've been trying to go through and remove those empty lines.

      --John

       

Log in to post a comment.