features 7.x-2.13

Hotfix release. Fixes regressions in 7.x-2.12.

Issues fixed:
#3181858: [regression] Primary key in 'features_signature' too big for MyISAM
#3183346: [regression] Overridden features are reverting upon update

How to upgrade

Whatever you plan to do, first make a database backup!
Run the pending database updates (test on a local or testing environment, before you do it on production).

Everything should be fine, but review anyway.

Recovery after 7.x-2.12

To determine if your site may have been affected by bug #3183346 in the 7.x-2.12 release, see the section "Which sites are affected" in #3183346: [regression] Overridden features are reverting upon update.

(after backup + db updates)

If you are absolutely sure that none of your features were overridden before the update, or that it is ok for these changes to be lost, you don't need to do anything.

If you want to recover local overrides from before the update, how you do this will depend on factors including how your site is set up and whether your features are specific to the site or provided by a distribution. Here are some tips that cover common scenarios. All scenarios require a full site backup from prior to the broken update. Adjust these steps to your own project's workflow. These tips are intended only as general suggestions. See also comments on #3183346: [regression] Overridden features are reverting upon update for tips on how site administrators have addressed the issue.

Custom site built with features

1. Get a database dump from before the update 7202 / release 7.x-2.12.
2. Deploy the dump on a local instance of your project.
3. Export the features (drush features-update-all).
4. Selectively commit those changes that you want to keep, into a new branch starting from master.
5. Deploy the branch on a test instance cloned from production, and revert the features to deploy the changes.
6. After successful testing, deploy the branch on production, and revert the features to deploy the changes.

Site based on a distribution

If you can add new modules to the server

1. Get a database dump from before the update 7202 / release 7.x-2.12.
2. Deploy the dump on a local instance of your project.
3. If not already installed, install the Features Override module.
4. Create a new feature module and export to it the features overrides that you wish to keep.
5. Commit the new feature module to a new branch starting from master. Also add the Features Override module.
6. Deploy the branch on a test instance cloned from production, and install the new feature module.
7. After successful testing, deploy the branch on production, and install the new feature module.

If you can't add new modules to the server

1. Get a database dump from before the update 7202 / release 7.x-2.12.
2. Deploy the dump on a local instance of your project.
3. Review all feature overrides.
4. On the live instance, use the admin UI to selectively recreate the overridden configuration.
5. Use the features admin UI to lock all overridden feature components.