Closed (fixed)
Project:
Features
Version:
6.x-1.x-dev
Component:
Code
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
30 Nov 2010 at 20:25 UTC
Updated:
1 Feb 2012 at 17:52 UTC
Jump to comment: Most recent file
Comments
Comment #1
joshuajabbour commentedComment #2
joshuajabbour commentedwrong issue, ignore this patch...
Comment #3
beeradb commentedThis fixes the notices for me, is dead simple, and is best practice anyway. RTBC on #1.
Comment #4
damienmckennaHere's another quick patch that fixes the same logic error in other places.
Comment #5
mikeryanLooks good, and eliminates tons of unnecessary notices when running simpletests for me.
Comment #6
wojtha commentedsubscribing
Comment #7
ryan_courtnage commentedPatch in #4 is good.
Comment #8
bleen commentedbump / sub
Comment #9
tim.plunketthttp://drupalcode.org/project/features.git/commit/80db53f
Comment #11
Sknight17 commentedI'm noticing the patch in #4 hides the 'state' when using drush in the command line. The state will still show up in the UI. However, this patch makes it impossible for those that use 'drush fl' as apart of their workflow. Is anyone else experiencing the same issue?
Comment #12
bcmiller0 commentedwe are hitting this case, but the actual data on hitting it shows $existing_instance[0]['widget_active']. Which seems like the patch avoids it but does a query update when it doesn't need to. as the widget_active is already set "1" but the existing_instance variable is an array when maybe shoudn't be.