Errors when upgrading and moving to new db/site.
Page: 1, 2
Recent posts in this topic
Ilija Studen
on Oct 6. 2006. 9:04 pm
TDS provided a good instructions. Just to clear things up about this: Run the update script.
If you are moving 0.7RC1 you do not need to run an upgrade script. If you are moving 0.6 that haven't been upgraded on old location than you need to run upgrade script.
Hope this makes sense.
If you are moving 0.7RC1 you do not need to run an upgrade script. If you are moving 0.6 that haven't been upgraded on old location than you need to run upgrade script.
Hope this makes sense.
activeCollab team member
Thanks TDS and Ilija! I'll need to try with you tips tomorrow. It sounds manageable. Appreciate you use the "regular English" instructions, as I may not be able to understand the "programer English. =P
Hope I can get it all set.
Hope I can get it all set.
The last couple of days, I've been trying to migrate my 0.7.1 site from the root folder of one server to a subfolder of a second server. One snag I ran into was in autoloader.php -- it's full of hardcoded paths to various php files. Before I edited that file, the main index.php page always returned 0 bytes. Afterwards, everything worked fine.
Perhaps autoloader.php could be modified to use the ROOT variable defined in init.php for finding the files it needs?
Perhaps autoloader.php could be modified to use the ROOT variable defined in init.php for finding the files it needs?
Ilija Studen
on Feb 9. 2007. 4:11 pm
Autoloader is completely dropped from new framework. Few months of use shown that it cause more problems than good. It makes sense using it while developing, but in production it caused only problems.
activeCollab team member
After purchase, I received a link to installation instructions, but no upgrade instructions. It would be EXTREMELY helpful to provide upgrade instructions alongside the install instructions (as is standard practice).
Trying to figure out how to manage the upgrade safely by reading through forum posts is confusing, as it references things like public/upgrade, while my "public" folder does not include an "upgrade" subfolder.
Trying to figure out how to manage the upgrade safely by reading through forum posts is confusing, as it references things like public/upgrade, while my "public" folder does not include an "upgrade" subfolder.
Ilija Studen
on Oct 5. 2007. 11:14 pm
Hi,
Old upgrade instructions do not work for v1.0. We have a module developed for this, but currently it has one big flaw - it cannot move files from the old setup (files from Files section and attachments). When we fix this issue we'll release the upgrade module. If you don't need to move the old files than development version of the module will do just fine. Just let us know...
Thank you!
Old upgrade instructions do not work for v1.0. We have a module developed for this, but currently it has one big flaw - it cannot move files from the old setup (files from Files section and attachments). When we fix this issue we'll release the upgrade module. If you don't need to move the old files than development version of the module will do just fine. Just let us know...
Thank you!
activeCollab team member
I can live without the old files (though I would eventually like to get these moved over, if possible, but not a huge deal for now). I just need a way to get 1.0 working - right now all I get is an apache listing of folders, no prompt to run an upgrade, no interface, no documentation or instructions on upgrading... nothing.
Honestly, I'm kind of shocked that this is the user experience I'm getting with a paid product!
Honestly, I'm kind of shocked that this is the user experience I'm getting with a paid product!
