Needs work
Project:
String Overrides
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
11 Jun 2011 at 00:55 UTC
Updated:
19 Sep 2013 at 21:03 UTC
Jump to comment: Most recent file
Comments
Comment #1
nico heulsen commentedsorry wrong thread
Comment #2
robloachShould be for both Drupal 6 and 7.
Comment #3
robloachNot 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.
Comment #4
matt v. commentedI generated a patch that bundles together the stringoverrides.features.inc and the info file change, so it can be applied automatically via Drush Make.
Comment #5
nlisgo commentedThis can be done with the strongarm module currently. Just save the settings:
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.
Comment #6
hefox commentedPlease use features_get_default here like other export/rebuilds so it's consistant and allows for altering
Revert/rebuild is suppose to move the override into the database for faux exportables like this, e.g. what rebuild is doing. For this, revert can call rebuild like other fuax exportables
There's unfortunately no good cleanup in features when items are moved out the export
I'm not sure if features is actually using this yet. I think that part of it's code hasn't been updated for d7, but might as well.
Haven't tested this yet as I think I'll just use strongarm for now (debating)