spaces 6.x-3.0

Coming from Spaces 2.x?

The Spaces 3.x branch makes significant departures from many of the concepts
in the 2.x branch. Here is a non-exhaustive list of important changes:

• Removed strict PURL dependency. Spaces can now be made active through means other than a PURL provider (see spaces_user_init()).
• Usage of CTools plugins API and export API.
• spaces_customizers() and spaces_settings() have been replaced with a general configuration override system using object controllers (more on this below).

If you are upgrading from Spaces 2.x, prepare for a rocky ride. Update scripts are included to migrate as cleanly as possible from 2.x to 3.x but any custom settings you have created will need to be managed manually. The update scripts leave the spaces_settings table intact for this reason.

Here is a rough list of steps to consider when upgrading from 2.x to 3.x:

1. Backup everything.
2. Run update.php.
3. Upgrade your features to Context 3, Strongarm 2, etc.
4. Have you implemented any custom 2.x space types? You need to migrate them, see API.txt and spaces.api.php.
5. Have you implemented any custom 2.x spaces settings? You need to migrate them to use standard Drupal variables and system_settings_form() (see the features_test module for an example).
6. Have you implemented any custom 2.x spaces customizers? The concept may not transfer cleanly to Spaces 3, or if it does, it will probably make the most sense as a custom controller.

Changes since DRUPAL-6--3-0-RC2:

• Removing stale references to Spaces Blog.