Details
-
Type:
Bug
-
Status: Done/Fixed
-
Priority:
Major
-
Resolution: Cannot Reproduce
-
Affects Version/s: 4.7
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Documentation Required?:Developer Doc
-
Funding Source:Needs Funding
Description
I'm not sure if this is documented anywhere (I haven't seen anything about it) but the way custom fields are handled appears to have changed in 4.7
Before, in 4.6, when accessing data with hook_pre we could expect the custom field to come through as 'custom_1' in the $params.
Now, in 4.7, the custom field name seems to have the ID of the value associated with it, ie: 'custom_1_-1' if it's a new value, or 'custom_1_4' (or similar) if it is an existing value.
This is a very significant change. Is it by design?