Problem/Motivation

For a site with many overrides, the process of manually exporting each existing override is slow and cumbersome.

Proposed resolution

We need a method to export some or all present overrides. Ideally this would have both UI and drush versions. For Drush, the following would be useful:

  • drush features_override_export all: : export all current features overrides.
  • drush features_override_package all newfeaturename: export all current features overrides into a new feature called newfeaturename.

Blockers

Would require a solution for #1314646: Provide default names and titles for overrides.

Comments

nedjo’s picture

nedjo
he/him/his
Primary language English
commented
Status: Active » Postponed

Postponed pending the work outlined in #1316940: 2.x Features Override using new Alter method. May not be needed after that issue is complete.

mrsean’s picture

mrsean commented
Version: 7.x-1.x-dev » 6.x-1.x-dev

Nedjo,

I know this is postponed, but for the 6.x version there is still a very real need to be able to pull all overrides out of the database at once, instead of explicitly manually up all overrides one at a time via the UI at /admin/build/features/features-override/add

Drupal Commons is still on Drupal 6.x, and I have made multiple changes ( greater than 100) to the Commons features.

Using the /admin/build/features/features-override/add UI will be like pulling teeth.

Is there no way to alleviate this for the 6.x-1.x branch? I even tried using the 6.x-2.x dev branch release(http://drupal.org/node/1524954), but it gave me several errors.

It seems like the default names issue would be resolved, since default names have been decided for 7.x-2.x, correct?

mrsean’s picture

mrsean commented
Issue summary: View changes

Updated issue summary.

zeip’s picture

zeip commented
Version: 6.x-1.x-dev » 7.x-2.x-dev
Issue summary: View changes

Changing the version to D7, since D6 is no longer supported but the issue still seems to exist.