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
Get a database dump from before the update 7202 / release 7.x-2.12.
Deploy the dump on a local instance of your project.
Export the features (drush features-update-all).
Selectively commit those changes that you want to keep, into a new branch starting from master.
Deploy the branch on a test instance cloned from production, and revert the features to deploy the changes.
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
Get a database dump from before the update 7202 / release 7.x-2.12.
Deploy the dump on a local instance of your project.
If not already installed, install the Features Override module.
Create a new feature module and export to it the features overrides that you wish to keep.
Commit the new feature module to a new branch starting from master. Also add the Features Override module.
Deploy the branch on a test instance cloned from production, and install the new feature module.
After successful testing, deploy the branch on production, and install the new feature module.
If you can't add new modules to the server
Get a database dump from before the update 7202 / release 7.x-2.12.
Deploy the dump on a local instance of your project.
Review all feature overrides.
On the live instance, use the admin UI to selectively recreate the overridden configuration.
Use the features admin UI to lock all overridden feature components.
features 7.x-2.12
Release notes
Regressions
See #3183346: [regression] Overridden features are reverting upon update.
If you have not already updated, do not do so. Instead, wait for a future release.
Fixes
3075578: implode() called with wrong parameter order in ctools_component_features_export_render(). (PHP 7.4)
features 7.x-2.13
Release notes
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 Get a database dump from before the update 7202 / release 7.x-2.12. Deploy the dump on a local instance of your project. Export the features (drush features-update-all). Selectively commit those changes that you want to keep, into a new branch starting from master. Deploy the branch on a test instance cloned from production, and revert the features to deploy the changes. 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 Get a database dump from before the update 7202 / release 7.x-2.12. Deploy the dump on a local instance of your project. If not already installed, install the Features Override module. Create a new feature module and export to it the features overrides that you wish to keep. Commit the new feature module to a new branch starting from master. Also add the Features Override module. Deploy the branch on a test instance cloned from production, and install the new feature module. After successful testing, deploy the branch on production, and install the new feature module. If you can't add new modules to the server Get a database dump from before the update 7202 / release 7.x-2.12. Deploy the dump on a local instance of your project. Review all feature overrides. On the live instance, use the admin UI to selectively recreate the overridden configuration. Use the features admin UI to lock all overridden feature components.
features 7.x-2.12
Release notes
Regressions See #3183346: [regression] Overridden features are reverting upon update. If you have not already updated, do not do so. Instead, wait for a future release.
Fixes
3075578: implode() called with wrong parameter order in ctools_component_features_export_render(). (PHP 7.4)
3086633: PHP 7.4 Compatibility - Curly brace syntax
2473935: Warning in features_help() if README.txt was deleted or made unreadable on deployment
2006432: Router item 'features/ajaxcallback/%' has bogus title callback.
3176326: Unknown column 'udated' in 'field list' - regression from #3162854
2644586: Wrong parent_identifier created for menu items
Performance
2989623: Performance enhancement: Skip menu_rebuild() when deleting multiple pages
Performance, data model changes
3162854: Move 'features_codecache' / 'cache_featurestate' to a dedicated db table 'features_signatures'
This replaces #1325288: Use regular cache table for features_codecache Code style, documentation
3082427: Code style fixes for inline comments
3081898: Misc code style fixes
3081268: Non-controversial whitespace code style fixes
3075616: Add @see comments on function strings, for easy navigation in IDEs.
3079939: Document hook_features_export_options_alter()
1758774: Document hook_features_disable_feature() and hook_features_enable_feature().
3060511: Enhance (function) doc comments in features.
Reverted Changes in the -dev branch since 7.x-2.11, that were reverted before this release 7.x-2.12.
3162809: Revert change on menu_links identifier logic from #2385853
This reverts #2385853: menu link shows as overridden: options identifier showing in default, not in overrides
3162806: Revert introduction of UUID entity path for menu links from #2353585.
This reverts #2353585: UUID export and import of menu items linking to nodes, terms and users