Welcome to Geeklog Saturday, September 21 2019 @ 07:24 am EDT

Geeklog Forums

Blank page after upgrade to GL 1.3.8


Status: offline

rv8

Forum User
Regular Poster
Registered: 10/10/02
Posts: 105
Location:Ottawa, Canada
I am trying to upgrade my local test site from GL 1.3.7sr2 to 1.3.8. My test site is running locally on Mac OS X 10.2.6. It worked perfectly before the upgrade. During the upgrade, I get a blank page when it goes to the success.php page, and if I try to go to the site pages. I’ve studied the path in lib-common.php, and the settings in config.php til I’m blue in the face, but I can’t see a problem. I also looked at the relevant FAQ entry. I wiped the whole thing clean, restored everything back to 1.3.7 from backups, and did the upgrade again with the same result.

I tried changing the various config.php database settings, but if I change any of them I get an error message about problems with finding the database server. If I put the correct values in, I get no error messages, so I figure they must be correct.

My GL site is buried in a directory one level below the /Library/WebServer/Documents directory (the Documents directory is the equivalent of public_html on other servers). But I’ve been careful to set up the $_CONF['path_html'].

Can anyone provide any hints as to what I may be missing, or how to troubleshoot?

Thanks.
Kevin Horton

Status: offline

Dirk

Site Admin
Admin
Registered: 12/01/02
Posts: 13073
Location:Stuttgart, Germany
Could this be a permissions problem? Are the files actually readable by the webserver? Anything in Apache\'s error_log file? bye, Dirk

Status: offline

rv8

Forum User
Regular Poster
Registered: 10/10/02
Posts: 105
Location:Ottawa, Canada
Quote by Dirk: Could this be a permissions problem? Are the files actually readable by the webserver? Anything in Apache's error_log file?

bye, Dirk


Dirk - Thanks for the pointer to the Apache error_log. I hadn't thought of it. It has lots of error messages in it that should be helpful.

I've got to head to work now and I'll dig into to GL later. I'll report back again once I've either sorted it out or need more help.
Kevin Horton

Status: offline

rv8

Forum User
Regular Poster
Registered: 10/10/02
Posts: 105
Location:Ottawa, Canada
I solved the blank page problem, but it highlights something that perhaps should be mentioned in the upgrade instructions.

My GL 1.3.7 install had several plugins and hacks. I suspected that there may be issues with between GL 1.3.8 and some of the plugins or hacks, so I decided to get a basic 1.3.8 installation working first, and then introduce the plugins and hacks one at a time.

I backed up the database, and all the GL files. I moved all the GL files to another directory, then unpacked the geeklog-1.3.8.tar.gz tarball. I edited the config.php and lib-common.php files, and followed all the upgrade instructions. At the end, I was rewarded with blank pages.

Following Dirk's hint, I looked at the apache error_log. It had numerous entries like:

PHP Formatted Code
[Thu Jul 24 07:51:48 2003] [error] PHP Fatal error:  main(): Failed opening required
'/Library/WebServer/plugins/menu/functions.inc' (include_path='.:/usr/local/php/lib/php')
in /Library/WebServer/Documents/rv8/lib-common.php on line 5146


It turns out that even though I there were no plugin files present, GL was still looking for them, as there is a database table that lists the installed plugins. I went into that table with PhpMyAdmin, and changed the pi_enabled status of all plugins (except the Static Pages plugin, which is part of the basic install) to NO. This solved my problem. The basic 1.3.8 install is working now, I just have to work my way through reinstalling the plugins, hacks and themes.

I think the instructions should recommend to either disable all plugins before the upgrade, or to be sure that all the plugin files are still present.

P.S. How the heck do you put long Code lines in the forum without either causing the window to end up too wide, or having line break tags show up?
Kevin Horton

Status: offline

Dirk

Site Admin
Admin
Registered: 12/01/02
Posts: 13073
Location:Stuttgart, Germany
Quote by rv8:I think the instructions should recommend to either disable all plugins before the upgrade, or to be sure that all the plugin files are still present.
Yeah, I guess the instructions could be clearer there. Point taken.
Quote by rv8Razz.S. How the heck do you put long Code lines in the forum without either causing the window to end up too wide, or having line break tags show up?
The CODE tag with the square brackets will not allow the lines to wrap - that\'s a feature. It\'s supposed to reproduce whatever you enter verbatim, including line breaks or lack thereof. As long as you don\'t have any text that Geeklog might try to interpret (like HTML tags), you could use the HTML code tag - that one does allow lines to wrap. bye, Dirk

All times are EDT. The time is now 07:24 am.

  • Normal Topic
  • Sticky Topic
  • Locked Topic
  • New Post
  • Sticky Topic W/ New Post
  • Locked Topic W/ New Post
  •  View Anonymous Posts
  •  Able to post
  •  Filtered HTML Allowed
  •  Censored Content