So I've been busy as heck the last month or so and just didn't have any extra time to devote to my site. I finally got things cleared up and decided: Now is a good time to update PGV and see what's new.
I followed my usual procedure and downloaded all the files to a local backup and backed up the db as well. Deleted everything except index/ media/ and config.php and then uploaded the latest SVN. I thought of upgrading to 4.2.1 first but figured I might as well try to go right to the bleeding edge.
Didn't work. Part of the header loaded and then it was just the loading image sitting there while nothing else happened. Oh well, not a total surprise, so I cleaned things out again and uploaded the backed up files. But nothing was working after that. Just a bunch of errors.
So after muddling things through for a bit I figured out my big mistake. Instead of backing up the original files to a clean folder I backed them up to an existing folder, which I forgot to empty first. So I got a mixture of files, some of which should not have been there anymore.
Lucky for me Sourceforge does have a very good SVN system. Much better than their forums. I managed to download a tarball of the last svn version that I had installed and working. Delete files, upload files... still not working but a different error message. Fooled and fiddled around for an hour before I actually read the error message properly. I'm working on a module and I used the research assistant as the starting point. So there was one block file that I didn't have on the server for that module that I did have in my local backup that conflicted with the block in the research assistant module. Deleted the file and finally had a working installation of PGV again. Woohoo!
But I think I'll wait until tomorrow to try and upgrade to 4.2.1. Had enough stress for one evening :-)
The moral of the story is: backup, Backup, BACKUP. But make sure you make a CLEAN backup or it's no dang good to you!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Stew
If you have the SVN installed/running, why downgrade to 4.2.1? What you are running is just as stable as the release code, if not more so.
-Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The version I was running before I tried to upgrade was something like 5082. So actually a bit older than 4.2.1. Current SVN version is 5391. So just too big of a jump I suspect. Probably caused by some missing tables I'm sure. The favourites selector didn't load so that's probably the issue but I didn't see any error messages to know for sure. Will check apache logs later.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Drat! Looks to me like I have PDO enabled for sqlite only. I think I will need to figure out how to compile php with support for pdo_mysql now. Big headache coming :(
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So I've been busy as heck the last month or so and just didn't have any extra time to devote to my site. I finally got things cleared up and decided: Now is a good time to update PGV and see what's new.
I followed my usual procedure and downloaded all the files to a local backup and backed up the db as well. Deleted everything except index/ media/ and config.php and then uploaded the latest SVN. I thought of upgrading to 4.2.1 first but figured I might as well try to go right to the bleeding edge.
Didn't work. Part of the header loaded and then it was just the loading image sitting there while nothing else happened. Oh well, not a total surprise, so I cleaned things out again and uploaded the backed up files. But nothing was working after that. Just a bunch of errors.
So after muddling things through for a bit I figured out my big mistake. Instead of backing up the original files to a clean folder I backed them up to an existing folder, which I forgot to empty first. So I got a mixture of files, some of which should not have been there anymore.
Lucky for me Sourceforge does have a very good SVN system. Much better than their forums. I managed to download a tarball of the last svn version that I had installed and working. Delete files, upload files... still not working but a different error message. Fooled and fiddled around for an hour before I actually read the error message properly. I'm working on a module and I used the research assistant as the starting point. So there was one block file that I didn't have on the server for that module that I did have in my local backup that conflicted with the block in the research assistant module. Deleted the file and finally had a working installation of PGV again. Woohoo!
But I think I'll wait until tomorrow to try and upgrade to 4.2.1. Had enough stress for one evening :-)
The moral of the story is: backup, Backup, BACKUP. But make sure you make a CLEAN backup or it's no dang good to you!
Stew
If you have the SVN installed/running, why downgrade to 4.2.1? What you are running is just as stable as the release code, if not more so.
-Stephen
The version I was running before I tried to upgrade was something like 5082. So actually a bit older than 4.2.1. Current SVN version is 5391. So just too big of a jump I suspect. Probably caused by some missing tables I'm sure. The favourites selector didn't load so that's probably the issue but I didn't see any error messages to know for sure. Will check apache logs later.
Well I went from svn 5082 to the 4.2.1 release with no problems. Next I'll try moving to the latest svn version and see what happens.
Drat! Looks to me like I have PDO enabled for sqlite only. I think I will need to figure out how to compile php with support for pdo_mysql now. Big headache coming :(