Active
Project:
Features Override
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
19 Oct 2011 at 16:24 UTC
Updated:
7 Dec 2011 at 15:51 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
mpotter commentedThis is high on my list to work on. The key to the alter hook in Features Field Override is that it gets called at the end of the normal Field exportable code. Figuring out where to call this alter hook within Features itself is tricky. But I'd definitely like to get this call out of the override exportable if possible since it causes issues with porting older features that don't have it. Also, I'd rather not change every single exportable to add an alter hook if a more general method can be found.
Comment #2
nedjoComment #3
nedjoDraft patch attached.
Comment #4
nedjoComment #4.0
nedjoUpdated issue summary.
Comment #5
mpotter commentedActually just solved this one. Newest patch to Features #1277854: Faciliate altering features, e.g., export field display settings separate from field data structure pushes the drupal_alter calls back into Features and takes them out of the specific exportables (like Field). Much cleaner now and no longer causes changes to be exported for existing features.
Comment #6
mpotter commentedTurns out that pushing the drupal_alter calls back into Features is not the correct solution. This only works for faux-exportables, such as Field. For a more "universal" solution, the drupal_alter call still needs to be made at the end of the actual exportable default_hook code.
Will be updating my sandbox and Features patch to reflect this later today and will post to the appropriate issue queues. Sorry for the confusion on my part...I was too focused on the specific Field override case, which is not representative of most other Features exports.
Comment #6.0
mpotter commentedUpdating for issue on features.