Background.

Upgraded server to MS Sql 5.1.37 and PHP to 5.3.0. (Host OS Mac OS X 10.6)

\path\to\www\geeklog
path\to\www\public_html

After completed existing Geeklog site (1.4.1) worked fine! No issues.

Decided to upgrade to 1.6.0sr2.

backed up site, then extracted geeklog 1.6 over top of existing directory structures.

Original config.php file located at path\to\www\geeklog\config.php (same directory where new config-db.php file ended up.

run: http://mysite/admin/install/index.php and get a screen that says it can't locate geeklog files asks for path to config-db.php file. Fine, enter it and the next screen I click "upgrade" and then I get a screen that says "Step 2: Enter Configuration info". At this point I have to think something isn't right... as I was led to believe from other posts etc. that the geeklog installer should have read my site config info from the existing config.php file. However all the fields on this screen are generic.

If I retype the info in and then click either Upgrade or Upgrade and configure additional plugins there is a bit of hard drive grind (perhaps 3 second) and then I just get a white screen. If I intentionally type in a correct username or password for the database then I get an error screen indicating that the credentials weren't correct so it would seem to be actually doing a lookup in the database.

I would appreciate any help.

Thanks so much.

Hello,

Do you have any logs info?

::Ben

---

I'm available to customise your themes or plugins for your Geeklog CMS

Unfortunately I'm not sure where to look for log info for the upgrade process... Apache error logs are clear of anything. Geeklog error file is blank.

Found a few other people now that had some issues that ended up first upgrading from 1.4.1 to 1.5.X then to 1.6.X.

So I tried that and the 1.5.2sr4 upgrade failed in the same exact way. (Restored the DB to the pre-upgrade version in between tries too)

Actually, the problem appears to be Mac OS X 10.6, not Geeklog. I had a lot of problems with my iMac at home as well and ended up having to build my own PHP and Apache to get it to work.

Here's one discussion from Apple's discussion boards.

bye, Dirk

Interesting discussion... thanks Dirk for pointing that out.

The thing that perplexes me at the moment is that I have a half a dozen different php/mysql test solutions running on this same box (including two Joomla and another geeklog site) and all of them run just fine after the migration. I thought at first that as long as it was just "reading" the attached mysql databases that perhaps there was no issue so I created a new user in joomla and it worked fine. I submitted a new article... worked fine. So database reads/writes both work with the Apache and PHP install from 10.6.

The discussion you pointed me to seems to indicate that if the proper "handles" are included in the mysql_close function in the code that things work fine. Is it possible that this is the case for geeklog 1.4.1, joomla etc? that perhaps the upgrade scripts don't have that specified?

Just wondering...

The funny thing is that Geeklog itself doesn't use mysql_close at all - only the install script uses it. And of the 3 occurences there, only one isn't using a db handle: The one in function mysql_v in lib-install.php. Try commenting out that line.

bye, Dirk

Dirk, okay so I took what you sent me and ran with it.

I used bbedit to search all the files in the admin/install directory for "@mysql_close"

I found two files with missing "handles":

lib-install.php and index.php

I commented out both lines and the upgrade went perfectly.

(This was upgrading to 1.5.2sr4 rather than 6.0.x)

I still don't understand why the GUI install doesn't suck the settings out of my config.php file though. Oh well, i am a happy user now.

Okay, I was looking at the code for 1.6.0 which is different in some places. And I was just able to confirm the changes on a machine with an unmodified Mac OS X 10.6 install. Instead of commenting out the mysql_close, you could also pass in the db connection handle like so.

Looks like that is all that is required to make Geeklog work on 10.6. I wish I had known that last weekend, it would have saved me a lot of work (and cursing ...).



It does that. But it leaves out a few things like the db information (for security reasons) and the stuff it asks you on the first page (like the site name and slogan). There was a technical reason for the latter - need to check if that's still true.

But everything else should be picked up just fine.

bye, Dirk

It also doesn't call mysql_free_result and there are some potentially big queries where it should. (Not to mention mssql_free_result and now pg_free_result. A new DB_ func should be added to support this.)