2.1: Upgrading
As of this writing there is still no quick upgrade path from the 1.x series of MomoKO. We have implemented and importer addin that will allow you to import your content, but not your settings or users, directly from MomoKO 1.x to 2.1. As of now there is no plans to bring this addin to 2.0 as 2.0 does not support switchboard/dashboard plugs.
We do advise upgrading as MomoKO 1.6 will no longer be supported as of the release of 2.1. If you have stayed with 1.6, simply switch back to the latest_stable branch after 2.1 is released. If you have already manually upgraded to 2.0 then your path is quick and painless now.
If you used git to acquire MomoKO you've already set up a local repository just log into your server via SSH and change over to the directory you install MomoKO in. Also, assuming you followed the instructions in the README you are already on the latest_stable branch. Just run git pull and git will update the software.
If you did no use the latest_stable branch (for example, if you skipped the 2.0 release and switched to 1.6-STABLE). You will have to switch branches. Simply run git checkout latest_stable. Do NOT switch to 2.1-RC or 2.1-STABLE unless you are a developer (see the note in the Installation instructions).
If you did not acquire MomoKO with git you will be able to acquire new MomoKO zip archives from FTP using the FTP procedures outlined above. The archive in /core/latest_stable/ will have been updated so you can simply re-download that if you wish or pick a version higher than the one you have in /core/
The easiest way to ensure your database is compatible with 2.1 is to set up a new one. You can use the same connection settings, but the best way to set this up is to delete your current "database.ini" and follow the instructions under "Configure MomoKO" in the README. Ensure you use a different table prefix. This will allow you to keep your old tables for reference later.
You can create an export of your old settings table using any MySQL client. The instructions to do so vary by client. Once the export is available, your can then import it into the new settings table. This will keep your settings the same on both installs.
The new user table should also be mostly compatible with the old one. You should be able to follow a similar procedure and import all your current users. If it fails, you may have to add them each in manually via the cli or dashboard tools.
You'll want to create a *.zip file with your pages, files, and folder in it. The easiest way to do this on a *nix system is to use zip. Go to the folder that contains your pages and files folder. On 1.1 this may be under the assets folder in your document root, on 1.5 and 1.6 these may be right under the root folder. You can always check your sites settings to find the exact folder. Once there run zip -r my-export.zip pages files to add the required folders to a zip file. This may get more complicated if your folders are in two different parent folders. In which case it is probably easiest just to make copies of the folders in the same parent folder and run the above command from there.
Go to your new MomoKO 2.1 site and log in as an administrator. Go to the new addin section in the switchboard sidebar and select 'importer'. Select MomoKO 1.0-1.6 as the type of data then browse for the zip file you just created. The importer will upload this file and prepare its contents for import into the new database. Select what data you would like to import then click import and the new data will be added.
In the future we may create a type of exporter for MomoKO 1.6 that will handle all of the above steps for you, from exporting the settings and users as well as zipping the contents of your pages folder.