@luisgzafra I know you made a lot of changes, so start by (1) backing up your database(s) and your entire site and (2) make a separate backup of every file you've changed. Be sure to get config.php and your .htaccess file in both backups. Also get the files/ and avatars/ directories _with their contents_. Be sure to notice permissions on the files and directories.
I'm not an expert at all, so these backups and the notes about permissions could keep you from losing everything if I forget something or get something wrong below. After you've made your backups, download them at home or the office, then make backups again. The biggest problems in upgrades come when you find out too late that you forgot to back up something important, so go ahead and make a second set of full, database, and changeset backups.
Next, stop the daemons. If you can afford to do so, I'd stop the web server also, so that no PHP processes are running while you're replacing files and copying your edits into the new versions of the files.
After that, you should be able to completely empty the directory where StatusNet is installed and place the new files into it. Copy your config.php and .htaccess files back into the directory. Copy the files/ and avatars/ directories back into place. Make sure you put the same permissions back into place. Check your notes to make sure you get this correct.
Next, run the scripts/checkschema.php, so that it can make any needed changes to the database. Here is the tricky part: you have to go back and re-edit everywhere you had changed and put your edits back into the new files. You may also find that some changes that were needed in 1.0.1 are not needed in 1.1.0.
After this, you should be able to start the web server and start the daemons. Before you let your users log back in, you should test to make sure that everything works as expected.
Be sure you keep those backups for at least a few days. Once your users get back on the system, they may find that everything except X works right.
There are probably shorter and easier ways to do this, but you've made some changes that you do not want to lose.
Comments
I'm not an expert at all, so these backups and the notes about permissions could keep you from losing everything if I forget something or get something wrong below. After you've made your backups, download them at home or the office, then make backups again. The biggest problems in upgrades come when you find out too late that you forgot to back up something important, so go ahead and make a second set of full, database, and changeset backups.
Next, stop the daemons. If you can afford to do so, I'd stop the web server also, so that no PHP processes are running while you're replacing files and copying your edits into the new versions of the files.
After that, you should be able to completely empty the directory where StatusNet is installed and place the new files into it. Copy your config.php and .htaccess files back into the directory. Copy the files/ and avatars/ directories back into place. Make sure you put the same permissions back into place. Check your notes to make sure you get this correct.
Next, run the scripts/checkschema.php, so that it can make any needed changes to the database. Here is the tricky part: you have to go back and re-edit everywhere you had changed and put your edits back into the new files. You may also find that some changes that were needed in 1.0.1 are not needed in 1.1.0.
After this, you should be able to start the web server and start the daemons. Before you let your users log back in, you should test to make sure that everything works as expected.
Be sure you keep those backups for at least a few days. Once your users get back on the system, they may find that everything except X works right.
There are probably shorter and easier ways to do this, but you've made some changes that you do not want to lose.
Probably would be easier to make the changes by hand, that change all the script, i think :)
Best regards.
Thanks!