This would be great to be able to customize the machine name of elements / fieldset (in code, machine name like new_1327593307149 may me hard to maintain and use) in this amazing module !

Comments

quicksketch’s picture

quicksketch
he/him
commented
Project: Form Builder » Webform Alternate UI
Component: Form Builder Core » Code

You definitely are able to customize the machine name in Form Builder. It even handles moving elements around in the array structure seamlessly, so you can rename a FormAPI key for an element and the element will stay in the exact same spot in the array (since order determines the implied weight). This request is probably meant for Webform Alternate UI, which hides Form Builder's ability to set form keys.

eme’s picture

eme commented

Thanks for the quick answer.

I must be blind. I'm working on the last 7.x dev version on form-builder-example page to generate a form and export it. There is indeed in code a form_builder_property_key_form which is a machine name type form element. It seems to be correctly called in form_builder_form_builder_properties (form_builder.properties.inc file). But the machine name field does not show up.

And if I do a dpm in form_builder_field_configure, there is indeed no key form field. Seems it is not a "property". And this function apparently does not refer to form_builder_form_builder_properties, but form_builder_get_element_properties. Must say I stayed there for the moment but I presume we should dig in it deeper.

quicksketch’s picture

quicksketch
he/him
commented
Project: Webform Alternate UI » Form Builder
Component: Code » Form Builder Core
Category: feature » support

Okay, cool moving this back over to Form Builder. The D7 version uses the new "machine_name" FAPI element to set the form key, but admittedly I haven't tested it with the demo module.

eme’s picture

eme commented

Ok. Seen. This indeed does not come from the core, but the example module. 'key' has not been defined as property in form_builder_examples_form_builder_types (form_builder_examples.module, 'properties' part of every fields). Seems to work if added.

eme’s picture

eme commented
Issue summary: View changes

amazing module btw