Closed (fixed)
Project:
Form Builder
Version:
7.x-1.x-dev
Component:
Documentation
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Nov 2013 at 09:31 UTC
Updated:
19 May 2015 at 09:44 UTC
Jump to comment: Most recent
Comments
Comment #1
fenstratI can confirm I've experienced this bug too. I've not got any time to look into it now but will do in the next 2 weeks.
Comment #2
sk2013 commentedThanks Fenstrat! looking forward a Solution to this issue. If you have some thoughts /ideas you can share it here. We will also try to find a solution.
Thanks
Comment #3
torotil commentedThat's a bit of a design-issue in form_builder so far: properties need to be put into the renderable array generated for the field. Under some circumstances form_builder reads them from the renderable. If the property is called 'custom' it's value needs to be stored under
$element['#custom'].Comment #4
fenstrat@torotil very interesting findings. This bug slipped off my radar but we're still effected with it. When time allows I'll get to testing what you outlined.
Comment #5
torotil commented@fenstrat: Usually
_form_builder_webform_form_builder_load_COMPONENT()can be used to set the needed #property values. Once this is done things should work as expected. Although this _is_ a workaround for the underlying design issue we can't really change this for form_builder-7.x-1.x. Perhaps this needs some kind of documentation.Comment #6
torotil commentedComment #7
torotil commentedI think I have a fix for this issue in #2464957: [META] Property values not loaded into form_builder (because of the 1:1 renderable mapping) - Please consider to help testing the patch.
Comment #9
torotil commentedI've committed the fix to 7.x-1.x. Please reopen if the bug persists.