Menu

Upgrade problem 4.2.2 to 4.2.4

Help
tthdoc
2011-01-30
2014-04-10
  • tthdoc

    tthdoc - 2011-01-30

    I am using localhost to upgrade from 4.2.2.to 4.2.4.  After the upgrade, all I get is a white screen.  Here is the exact procedure I used.

    1.  I had 2 identical folders in htdocs - 422 and 424.
    2.  Go to localhost/422 and localhost/424 and both work fine.
    3.  Download 4.2.4 all zip file and unzip.
    4.  In 4.2.4 folder, delete config.php, delete index folder and delete media folder.
    5. Go to localhost/424 folder and KEEP config.php, index folder,  media folder and languages folder.  Delete all remaining files.
    6. Go to languages folder and delete everything except extra.en.php.
    7. Go to 4.2.4 folder, select all and copy.
    8. Go to localhost/424 folder, paste, and say yes to all for warning about languages folder already existing.
    9. Go to localhost/422 - all looks good, go to localhost/424, blank white screen.

    What did i do wrong or miss?

    Thanks,
    Doc

     
  • tthdoc

    tthdoc - 2011-01-30

    Forgot to add, after step 6 I deleted the cache folder in the index directory and the reports.dat file in localhost/424.

    Doc

     
  • Gerry Kroll

    Gerry Kroll - 2011-01-30

    You've probably set your memory limit too low in the php.ini file.  PGV needs at least 32 Mb, and the more you can let it have, the better.  The other thing to watch for is that you have the file and folder permissions correct.  On most *nix systems, 644 would be OK, but on the systems I'm using, I have to set permissions to 755.  The extra "1" in each digit means "execute".

     
  • Gerry Kroll

    Gerry Kroll - 2011-01-30

    I forgot to say:

    Does the page source of your supposedly blank page reveal anything?  Sometimes you can see a meaningful error message at the bottom of the page source.

     
  • tthdoc

    tthdoc - 2011-01-30

    Memory limit set to 128M.  Not sure how to set file permissions on a local host.  As to page source, I checked and it comes up completely blank.

     
  • tthdoc

    tthdoc - 2011-01-30

    Don't know if this helps but I modified the index.php file as follows:

    echo"test";
    define('PGV_SCRIPT_NAME', 'index.php');
    echo"1";
    require './config.php';
    echo"2";
    require_once PGV_ROOT.'includes/index_cache.php';
    echo"3";
    require_once PGV_ROOT.'includes/functions/functions_print_facts.php';  //-needed for the expand url function in some of the blocks

    if (!isset($CONFIGURED)) {
    print "Unable to include the config.php file.  Make sure that . is in your PHP include path in the php.ini file.";
    exit;
    }

    The output I get is test1. 

     
  • tthdoc

    tthdoc - 2011-01-30

    A little further sleuthing around.  I used echo statements to see where they stopped showing.  I found the problem in the sessions.php file.  Around line 224 you have this:

    // If we have a preferred URL (e.g. https instead of http, or www.example.com instead of
    // www.isp.com/~example), then redirect to it.
    if (!empty($SERVER_URL) && $SERVER_URL != PGV_SERVER_NAME.PGV_SCRIPT_PATH) {
        header('Location: '.$SERVER_URL);
        exit;
    }
    

    If I  put an echo statement before the header line, it shows up, so the script is executing here.  One problem I found was the $SERVER_URL was coming up as C:/xampp/htdocs/FamilyTree422.  I thought this was the problem (being 422 instead of 424), so I hard coded before the header line:

    $SERVER_URL = 'C:/xampp/htdocs/FamilyTree424';
    

    Still no go.  But it seems that this is where the script is halting at.

     
  • Gerry Kroll

    Gerry Kroll - 2011-01-31

    Check file "config.php".  The $SERVER_URL value should be empty.

    When this value is empty, PGV will use the URL path that you used to launch PGV.

    I don't think the "c:/xampp/htdocs/" part is right here.  On a normal system (I'm not at all familiar with XAMPP), you would find the real URL here.  For example, I have two systems, one of which is on my laptop, the other is on a real server.  The laptop runs Linux in a coLinux window on the underlying Windows XP system.

    On the laptop, I launch PGV by typing "http://localhost/PGVTest" into the browser's address bar and the $SERVER-URL value is "http://localhost/PGVTest", but the entry in config.php is still empty.  The value is calculated when PGV starts.

    On the real Linux server, PGV is launched by typing "http://keldine.ca/phpGedView" into the browser's address bar and the $SERVER_URL value is "http://keldine.ca/phpGedView".  Again, the entry in config.php is empty.

    By leaving the $SERVER_URL entry in config.php empty, you can change the directory structure in which PGV lives without having to reconfigure it.

     
  • tthdoc

    tthdoc - 2011-01-31

    Thanks, that fixed the problem.  I guess the question is why did the 422 directory work ok?  It  had the $SERVER_URL = 'C:/xampp/htdocs/FamilyTree422';  Oh well, as long as it works.  The other question is one that happens everytime I upgrade (which is why it takes so long to do it and I don't look forward to it).  I use a modification of the simplyblue template.   After the upgrade it has the cloudy theme.  I checked the gedcom configuration under user options and it shows cloudy and next to it in the type in box lists my custom theme and in red next to it says: themes/custom_theme416/ does not exist.  Obviously this is because everything was deleted before the upgrade.  If i just put back the custom_theme416 folder, would it not be easier to do a compare of the newest simplyblue file and my old modified file, and then tweak mine?

    Thanks

     
  • Gerry Kroll

    Gerry Kroll - 2011-01-31

    What you really want to do is to compare the version 4.2.4 "simplyblue" theme with the one in version 4.2.2.  This will give you the differences that you need to port into your modified theme.

    Re: "copy the old theme":  Yes, by all means, start there.  Unfortunately, I can't tell you what changes were made to the themes.

    Check for changes to the "images" subdirectory, to the "style.css", "theme.php", "header.php", "footer.php", and "toplinks.php" files.  If the SVN version numbers at the top of the various files are the same between the old and the new files, you don't need to check any further.  Don't go by the date & time of creation.

    When doing the file comparisons, you might wish to look at KDiff3.  I've found this program to be very useful.  http://kdiff3.sourceforge.net/

     
  • tthdoc

    tthdoc - 2011-01-31

    Thanks for all the help. I use WinMerge and found it very useful for this.  I try to remember whenever I change a file to put a comment line of "changed by Doc" at the top of the file, and then right before lines I changed.  This helps by using GREP to at least locate which files were changed.   Since I made 2 copies of the site and put one in a 422 folder and one in a 424 folder, then did the upgrade, I will now just use WinMerge to compare the 2 folders, and go from there.  Hopefully won't be too bad.  I will just do as you suggested and compare the 2 simplyblue themes from the 2 versions, and then I can go back and make any tweaks to my modified simplyblue to match.

    Thanks again.
    Doc

     
  • Chris

    Chris - 2011-08-03

    I am having the same problem upgrading from 4.2.2 to 4.2.4, White screen after upgrade.
    I then did the upgrade from 4.2.2 to 4.2.3 with no problems.
    I have checked - there is enough memory and tried removing the url in the config file. Still no joy

     
  • Gerry Kroll

    Gerry Kroll - 2011-08-03

    If you have a white screen, you should examine the page source.  Quite often, there's a meaningful error message, not generated by PhpGedView, at the bottom of that page source.

     
  • Sarunas K

    Sarunas K - 2011-08-04

    I am having a problem with user accounts. After upgrading from 4.2.2 to 4.2.4 all users lost full names and registration date. I can see all data in database but phpgedview can not. Also gallery2 stopped to work. Getting the following error:
    ERROR 8: Undefined index: scheme
    0 Error occurred on line 69 of file pgv.php in function mod_gallery2_load
    1 called from line 39 of file index.php in function mod_gallery2_run
    2 called from line 34 of file index.php in function require_once
    3 called from line 89 of file module.php

    ERROR 8: Undefined index: host
    0 Error occurred on line 69 of file pgv.php in function mod_gallery2_load
    1 called from line 39 of file index.php in function mod_gallery2_run
    2 called from line 34 of file index.php in function require_once
    3 called from line 89 of file module.php

    ERROR 2: Cannot modify header information - headers already sent by (output started at /data/www/gedview/includes/functions/functions.php:500)

    Any ideas?
     

     
  • Gerry Kroll

    Gerry Kroll - 2011-08-04

    @sarunask:

    1. Please do not hijack someone else's thread.  Your problem is completely different from the "blank screen" problem in the original post.

    2. When you upgraded, did you run the Install wizard (site configuration) and then re-import the GEDCOM?  Even though you don't actually need to change any of the site configuration options, you should still go through the motions as if you did do so.

    3. You did not ugrade the Gallery2 module when you upgraded the rest of PGV from 4.2.2 to 4.2.4.  The error on line 69 of pgv.php indicates that you are in fact running Gallery2 as distributed with PGV version 4.2.2.  If you had upgraded to the version of Gallery that's part of the 4.2.4 "full" distribution, the error would have occurred on line 71.

    4. After having installed the correct version of Gallery2, please change line 68 of file "modules/gallery2/pgv.php".
    Original line:

    $bits = parse_url($SERVER_URL);
    

    New line:

    $bits = parse_url(PGV_SERVER_NAME.PGV_SCRIPT_PATH);
    

    If this cures the problem, please let us know so that the SVN repository can be updated accordingly.

     
  • Sarunas K

    Sarunas K - 2011-08-04

    Thank you for quick answer and sorry for posting in wrong plase. I will start a new thread.

     
  • Chris

    Chris - 2011-08-04

    The source is also completely blank.
    The working 4.2.3 is at www.booysen.org/phpgedview/index.php I have the new 4.2.4 on http://www.booysen.org/phpgedviewnew/index.php

     
  • stesch79

    stesch79 - 2011-10-07

    The source is also completely blank on my updated PGV.

     
  • Gerry Kroll

    Gerry Kroll - 2011-10-07

    Memory limit in php.ini is too low.  PGV needs at least 32 Mb, and sometimes even 32 Mb isn't enough.

    PLEASE DO NOT HIJACK OTHER POSTS - START YOUR OWN.

     
  • Chris

    Chris - 2014-04-10

    I have a problem with another blank screen. Not the memory issue.

    www.hanekom.org.za/phpgedview/index.php

     
  • Gerry Kroll

    Gerry Kroll - 2014-04-10

    Chris:
    Please start your own thread.

     

Log in to post a comment.