Documentation for Crowd 2.7. Documentation for earlier versions of Crowd is available too.

Skip to end of metadata
Go to start of metadata

Below are instructions on upgrading an existing Crowd installation to the latest version of Crowd. There are two upgrade procedures to choose from:

  • Method 1: Automatic database upgrade. Install the new version of Crowd and simply point it at your existing home directory. The upgrade procedure automatically updates your Crowd database.
  • Method 2: Data transfer via XML backup. Back up your Crowd database to XML before starting the upgrade, install the new version of Crowd and then import the data into your new Crowd installation.

Recommended Upgrade Procedure

If you are upgrading from Crowd 2.0 or later, you can use method 1, automatic database upgrade or method 2, data transfer via XML backup.

Upgrading from Crowd 1.6 or earlier

If you are upgrading from a version of Crowd prior to 2.0, please make your choice based on your database server, the version of Crowd you are upgrading from and the version you are upgrading to.

Alternatives

These are some options you may like to consider:

  • If you prefer method 2, data transfer via XML backup, you can choose that option for any database server and no matter which version of Crowd you are upgrading from or to.
  • If you are upgrading from Crowd 1.2 or earlier, are using PostgreSQL, MySQL or Microsoft SQL Server, and cannot perform an XML backup:
    1. Upgrade to Crowd 1.6 first, following the instructions in the Crowd 1.6 upgrade guide.
    2. Then upgrade from Crowd 1.6 to Crowd 2.0.4 or later, using the automatic database upgrade as described in the Crowd 2.0 upgrade guide.
  • If for some reason you must upgrade to Crowd 2.0.0, 2.0.1, 2.0.2 or 2.0.3 (and cannot upgrade to Crowd 2.0.4), follow method 2, data transfer via XML backup.
RELATED TOPICS

5 Comments

  1. This guide is a bad joke, it doesn't even tell you which files you should keep, like build.properties or what you have to run.

  2. Anonymous

    This is just an overview.

  3. No, this is a "let's put it here so no one tells us we have no upgrading guide" thing. It is a joke...

  4. After upgrading from Crowd 2.2.2 to 2.6.4 we are no longer able to use the "isCurrentUserInGroup" method inside of the default.jsp to restrict access to custom links. Please assist.

  5. I agree that it could be a little bit clearer that you must read the details by following these links:

    Upgrading Crowd via Automatic Database Upgrade
    Upgrading Crowd via XML Data Transfer

    But if you do, I think it's pretty detailed.