Geeklog Forums

Hi all,

I'm planning on upgrading to 4.1 from 1.4.0sr5-1. I'm happy installing it myself and working out the problems as I go along, but I just want to make it as easy as possible for me to back out if I screw things up.

1) Is it possible to install it into some other directory, or in some kind of sandbox, so that it doesn't affect my main site while I test it? And then switch the now-upgraded code into the main site in one step?

Ok, that's probably unlikely, so let's look at the approved solution: keeping the main site in some other directory while the main site is upgraded:

2) I have a site that is all installed in the webroot -- I'm using GoDaddy and I can't get access to the level below. So my files are all in path/to/webroot. Should I move them all to path/to/webroot/backup while I work on upgrading?

3) Let's say I screw up royally and can't get anything working. Will backing out (that is, returning everything to the way it was before) be as simple as moving my backup from path/to/webroot/backup back to path/to/webroot? Will anything else have changed? I've just backed up the database -- will that be easy to roll back if things get messed up?

Thanks for any help -- just a little nervous about upgrading while my site is live!

Sam

There`s a good FAQ for moving sites:
http://www.geeklog.net/faqman/index.php?op=view&t=37

Basically it is as easy as you say. Just try to copy your site to say /testing/ then change the paths and copy the MySQL. So you would have cloned your site and you can do the upgrade without risk. Finally you can replace the original with the updated clone.

Usually you stumble over some smaller problems like the rights of subdirectories which you forgot to set to 775 or so. Sometimes you can`t access uploaded pictures of stories on the server by FTP. This depends on the server settings.

Hmmm... So I copied the entire contents of my site into an /upgrade/ folder. You can see it here: http://www.ai-tools.org/upgrade/.

However, all the links still point to the non-upgraded locations. I tried changing the path in the /upgrade/ config.php file, but that didn't do anything (I can't remember, are those values only used during install?).

So the upgrade version is not self-contained. Naturally I don't want to change all the links by hand, because then moving it back into the root will be a much longer process. Also, should I be duplicating the database, or can I leave both versions pointing to the same one?

Yes >>copy the MySQL<< duplicate it!

>>change the paths<< Yes, you need to change the paths in config.php (at the beginning sections 1-3) and lib-common.php manually.

And please look at the FAQ.

Sorry, I only mentioned config.php. Actually, I changed the paths in both config.php and lib-common.php.

config.php:


lib-common.php:


Still, when I go to http://www.ai-tools.org/upgrade, all the links point back to http://www.ai-tools.org/whatever.

That's why I was asking if install needs to be run again. But if that's the case, I can't make my upgrades in the /upgrade/ location and then move it all back to root, because then the urls will be wrong again!

I assume I'm confused somewhere...

Ah, I guess there was one other line that I had to change in config.php:

It seems to work now, except for the hard-coded urls in the navigation menu.

Thanks!
Sam

Ok, so I made a new folder, duplicated my database, edited my config and lib-commons files and started the install script. I then started installing, and received an error almost immediately because it couldn't find lib-commons. So I went and made sure the permissions on lib-common were 775. I then went back to step one of the install script and clicked "next" again.

Now I get an error:

1062: Duplicate entry 'Syndication Admin' for key 2

I'm guessing it's because it's trying to do the same things in the install again. If that's so, how do I get it to start fresh?

I saw an entry in gl_groups for syndication admin, but nothing about keys.

Update

Then, instead of just clicking back to Step 1 and trying to get to Step 2 again, I went all the way back to Step 0, and clicked forward into Step 1. Now it says "Database already up to date!"

Can I be certain that it really is up to date, and the syndication admin error is nothing? What was that all about, anyway?

So 1.4.0sr5-1 was runing perfectly as a copy, right? Now you want to update to 1.4.1 is it? You copied over the new 1.4.1 and you are now in the update process?

Yes that's correct. I'm just not certain that the database updated correctly, or what was going on with the error messages.

Anyway, it seems to be mostly working now, except for some of the css being off, and the fact that if I try to "Mass delete comments" using Spam X it hangs for a while and then goes to a blank screen...

You could try it again and upload the MySQL once more.

lib-common.php doesn`t have to have 775.