Upgrading

  1. Always back up your database in case something goes wrong during the upgrade. For instructions, see Backing up an Omeka Database.
  2. Deactivate your plugins in Settings > Plugins of the administrative panel. Plugins must be upgraded to be compatible with the version you're upgrading.
    • Be careful not to uninstall the plugins, because you may lose data. See Upgrading Plugins for more information.
  3. Move your old Omeka installation out of the way, either to somewhere else on your server or transfer the files to your local computer.
  4. Download and unzip the latest version of Omeka into the empty directory where your previous install of Omeka was located.
  5. Move or copy the following files and directories from your old Omeka folder to the corresponding location in your new Omeka installation (if copying, make sure you keep all permissions the same as they were before):
    • db.ini (in version 0.9, this was located in application/config/db.ini; since version 0.10 this has been relocated to the root of your installation.)
    • archive/
    • If you are upgrading from 1.x to 2.x rename archive to files, and rename the files/files in the directory you just renamed to files/original
    • Any themes or plugins you had installed. The "bundled" themes and plugins will already have been updated with Omeka, so you don't have to move them back over.
    • If you've modified any of Omeka's core files, you'll need to move those changes over too (be careful with this, as the original file may have been changed in newer versions).
  6. Finally, you may need to upgrade your database. Go to your site's administrative panel in your web browser.
    • If a database upgrade is needed, you'll automatically be redirected to an upgrade page (example.com/admin/upgrade). Click "Upgrade" to update your database to reflect the new data model and finish the upgrade. Omeka 1.2.1 and earlier only: Instead of redirecting, older Omeka versions will show an alert on your dashboard with a link to follow if the database needs to be upgraded.
    • If you weren't redirected when you went to your administrative panel, then no database changes were required, so you're done!