Geeklog Forums

All seems to go well, until I try step two. I choose to upgrade from 1.3.9, but I get the following after hitting the submit button:



Any ideas? Please help. Thanks.

---

Jhary

Hmm, that seems to refer to an empty SQL query. Not sure how that should have happened, though.

Any chance you could switch on error_reporting or add some debugging statements to find out where exactly it actually throws this up?

bye, Dirk

yes yes, i just received the same error upgrading 1.3.9sr1 to 1.3.11
on the second try, i received a duplicate column error--so some part of the script was executing anyway. that's not really a good thing tho.

update: it seems that, tho this error continues each time i try to upgrade after restoring my backed up db, the upgrade process does in fact upgrade the database leaving a functional site--at least in my case.

I'm still working thru the process to see if I can find something there, doubtful, but who knows... i'll let you know.

so, it turns out that the upgrade does happen tho the error is returned, at least in my case... for reasons unknown to me however, once the redirect to success.php is echoed, then the script/query fails. I see no query that would be empty except those involved in building the header for success.php, but there is no reason for them to fail/be empty.

IMO, the meta refresh didn't work is all--cause or result, i don't know. the $_CONF['site_admin_url'] was being overlooked somehow.

that's as far as I got and as far as I'm going. sorry if that is no help

1.3.9 sr1 is actually 1.3.10, use that for the database upgrade and it should work.

What???

I can confirm the "empty request" error message, but it seems to have done all the necessary database changes anyway. Need to investigate further ...

bye, Dirk

Okay, AFAICS,

• it only happens when upgrading from 1.3.9 or earlier versions


• despite the error message, the actual upgrade seems to work just fine


• this version should fix it

Can someone confirm this, please? I'll update the tarball then ...

bye, Dirk

yes yes, that did it... tested on 1.3.9.
nice job Dirk

Indeed, my upgrade does work, even though I received the error. I reinstalled my old database and tried the upgrade again, and the same error occurred, but it still works. Just worried me there for a moment. Thanks, Dirk.

---

Jhary

Yes, I also encountered the error when upgrading from
1.3.9. Thanks for getting out a quick fix.

One note. I rather foolishly just right-clicked on Dirk's fix (link)
above and saved it to disk -- thinking it was a straight php file.
Don't do that. The link leads to an HTML page with a CVS
view of the file. I had to select the php code from the HTML
page, then save into a file.

There's a download link in the upper right corner of that page. Use that ...

bye, Dirk

Should have read this posting before I installed . Sigh...

All the same, Thanks Dirk for the quick fix on install.php.

In the meantime, can anyone please confirm if the upgrade after getting "1065: Query was empty" is sound? Or do you recommend that we roll back to re-install?

Thank you so much.

I have been trying to get this upgrade working for a couple of days now. I currently am running 1.3.9sr2 and am trying to upgrade to 1.3.11. In doing so, I have not edited the downloaded files other than what is given in the directions. This means mycal and weather plugins are left on the roadside (though the database stuff will still be there I guess).

The problem I am encountering after running the install.php page (the new one, thanks Dirk) is a simple blank page. Nothing. :-(

I can't get any pages to show up, not even the check.php page. The only single page I can see is the install/info.php

I have set permissions to 777 in an attempt to get everything working, but that didn't help (this is on my laptop-test-bed so whatever).

Oddities I noted: If I mess up the config.php file, I can get geeklog to complain about not being able to connect, so I know things are churning in there. My geeklog/logs remain blank however.

Setup:
Prior Geeklog: 1.3.9sr2 (worked great)
PHP: 5.0.1 from entropy.ch
MySQL Client API version 4.1.3-beta
(phpMyAdmin says: MySQL 4.0.20-standard-log running on localhost)
Apache: 1.3.33 (Darwin)
MacOS 10.3.7

I am going to try going back to php 4.3.4 whatever I had before. Any other advice? How do I turn on the error_reporting you mentioned?

Thanks!

In your php.ini, set

error_reporting = E_ALL

and

display_errors = On

Restart the webserver and try again. It should display an error message instead of the blank page then.

bye, Dirk

Thanks. Since you didn't shoot me for using PHP 5.0.1, I went ahead and stuck with that version.

The error I am getting from install/check.php is:

Now, I am using the files downloaded from the site, which contain no 'weather' stuff in the plugins directory. I can only guess that there is some stuff left in my original database that used it. Could that be the case?

Do I need to disable that plugin (and all plugins) before I upgrade? How do I proceed if a plugin has a problem with this version of Geeklog? I am worried about customizing my site TOO much and making these upgrades painful.

Thanks for the quick reply.

If you don't have the files for the plugins installed, you will have to disable it.

Geeklog keeps a flag for each plugin that is installed and enabled, and tries to load the plugin's functions.inc then.

So use phpMyAdmin or whatever you have handy, and in the gl_plugins table, set the field 'pi_enabled' to 0 for every plugin that you don't have installed (i.e. for which you don't have the files). Your site should work then (no need to run the install script again).

bye, Dirk

Thanks, that worked and I can see pages now. I am going to go back and go over the entire process again after adding the code to the appropriate lib-XXX pages to see what caused the site to barf in the first place.

Is this a common problem? Are there some plugins that just won't work (until they're updated), or should things be seamless?

Thanks for the insight.

Plugins that don't require changes in Geeklog's core code should usually work just fine, i.e. they should not be affected by an upgrade.

If the plugins are enabled when you do the upgrade and you don't have their files installed, then that was probably your problem ...

bye, Dirk

Well, the upgrade went fine, thanks again.
The only thing that I might have done different (unless I am mistaken, I might have just simply missed something) is copying the new "professional" theme into the 1.3.9 version and setting that as the default in my config.php file whilst still running 1.3.9. I haven't yet tested with the older themes as I usually don't give my users the choice.

Now on to my production sites!