Geeklog Forums

Hi, so I used to have a very customized V1.3.6 of geeklog. But i figured it was about time to upgrade.

I had many probems with my database while upgrading, but from what i saw from the source code i assumed it was pretty much succeeded. I had an SQL error. But could not trace its origin.

So i ignored that alltogether, and basically just copied the follwoing files, overwriting my old ones:
geeklog-1.3.8-1sr4/config.php
geeklog-1.3.8-1sr4/docs/changed-files
geeklog-1.3.8-1sr4/docs/changes.html
geeklog-1.3.8-1sr4/docs/config.html
geeklog-1.3.8-1sr4/docs/history
geeklog-1.3.8-1sr4/docs/install.html
geeklog-1.3.8-1sr4/public_html/admin/block.php
geeklog-1.3.8-1sr4/public_html/admin/event.php
geeklog-1.3.8-1sr4/public_html/admin/group.php
geeklog-1.3.8-1sr4/public_html/admin/link.php
geeklog-1.3.8-1sr4/public_html/admin/poll.php
geeklog-1.3.8-1sr4/public_html/admin/story.php
geeklog-1.3.8-1sr4/public_html/admin/topic.php
geeklog-1.3.8-1sr4/public_html/admin/user.php
geeklog-1.3.8-1sr4/public_html/calendar.php
geeklog-1.3.8-1sr4/public_html/calendar_event.php
geeklog-1.3.8-1sr4/public_html/comment.php
geeklog-1.3.8-1sr4/public_html/submit.php
geeklog-1.3.8-1sr4/public_html/usersettings.php

My website loaded flawlessly, however, none of these files would actually work. The permissions are correct, but basically, i try to submit a story and the geeklog header and left blocks show, but not the submit story part.

I am honestly puzzled.

If anyone had a similar probem please help me out.

Essentially, if i get that SQL error, is my database ready to go? I mean is this problem database related?

Well, I hope you made a backup of your database before you attempted to upgrade ...


That was a bad idea. If you get MySQL errors during the upgrade, it means that the upgrade did not succeed. Which means you now have a database that's halfway upgraded and is not compatible with either the old or the new version ...


That list is a bit short. In particular, I'm missing the system directory.

I would strongly suggest that you restore the database to its state before the failed upgrade. Then replace all the files (basically as if you were doing a fresh install). Then run the install script in upgrade mode and make sure to select the correct version you're upgrading from (it will default to 1.3.7, but you said you were on 1.3.6).

bye, Dirk

No worries, i have all of the necessary backups... Including database, so for now, i am running the new (half new) database, with the old files. The irony, because it works just fine.

Basically on the bottom of my page it states that this is geklog 1.3.8 while all of the files are back to what they used to be for 1.3.6...

I don't get any errors, none in the error log, and none when i load those pages.

Now, could you be so kind as to indicate to me which other files do i need for the dependencies.

I relied particularly on that list. This is because i have done lots of hacks to the main source code, mainly when i was confused and knew little of PHP. So going through and fixing all is impracticable while replacing every file, makes me feel bad

I am sorry i am bumping this story after such a while, but i would reallly appretiate a quick and accurate changes file. As i state above, the changes file included in the newest geeklog seems incomplete as I am missing something, because none of the upgraded files work, i am assuming dependencies issues.

Thanks,

You shouldn't use any of the upgrade archives, but the full 1.3.8-1sr4 tarball. Than, as stated above, make sure you've replaced all the old files and it will work.

bye, Dirk