Closed (fixed)
Project:
Features
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Feb 2011 at 19:47 UTC
Updated:
10 Aug 2019 at 20:26 UTC
Jump to comment: Most recent
I was having a lot of trouble with drush fd sometimes acting as if it's diffing against something nonexistent. After a lot of debugging I determined that $module->info['features']['field'] was becoming $module->info['features'][0] somewhere. I finally traced it to features_get_info() handing out the original object (so it is acting like a reference)
This patch fixes the problem I was having, but I don't know if it's proper or covers all cases.
| Comment | File | Size | Author |
|---|---|---|---|
| features_fix_diff_user_fields.patch | 731 bytes | bdragon |
Comments
Comment #1
bdragon commentedWhoops, I had this in the wrong queue.
Comment #2
irakli commentedCommitted: http://drupalcode.org/project/features.git/commit/ce0fe96
Thank you
Comment #4
donquixote commentedThis is long time ago, but...
It does not.
In the case where $name is provided, a cloned object will be returned.
However, if $name is NULL, the array of original objects will be returned, allowing other code to manipulate the objects.
In fact, the function is itself guilty of modifying the original objects from Drupal core's system_rebuild_module_data() (only happens on reset/rebuild), adding the ->components key.