Project:String Overrides
Version:7.x-1.x-dev
Component:Code
Category:feature request
Priority:normal
Assigned:Unassigned
Status:needs work
Issue tags:Features integration

Issue Summary

Is having Features module support something that's desired? Export individual/mass String Overrides as a Feature... I understand this kind done for all string overrides with Strongarm, but would having individual string exports be handy?

Let me know!

Comments

#1

sorry wrong thread

#2

Status:postponed (maintainer needs more info)» active

Should be for both Drupal 6 and 7.

#3

Status:active» needs work

Not sure why it doesn't report conflicts when overrides are changed. Stick in as stringoverrides.features.inc and stick in files[] = stringoverrides.features.inc to the info file.

AttachmentSize
stringoverrides.features.inc_.txt 4.45 KB

#4

I generated a patch that bundles together the stringoverrides.features.inc and the info file change, so it can be applied automatically via Drush Make.

AttachmentSize
stringoverrides-features_support-1185284-4.patch 5.12 KB

#5

This can be done with the strongarm module currently. Just save the settings:

  • locale_custom_disabled_strings_en
  • locale_custom_strings_en

It would be great to have features capability here but the patch doesn't work. No errors are thrown, you can create the feature and see all of the individual settings but you can't detect a difference between the code in the feature and what's in the database and therefore cannot revert.

The weakness of the strongarm method is that it means you have to bundle all of the string overrides in one feature.