Hi, just posting this to confirm I’m not going mad.
I have a plugin or two which use text fields named “element_id”. Today, they’re broken, as properties.element_id is suddenly returning what I believe is an internal Bubble ID value- for instance #bTHBg2, rather than whatever the user input in the text field. Has Bubble added properties.element_id as a way to retrieve the internal ID of the Bubble element? If so, I would have thought that properties.bubble.element_id would be more appropriate, no?
Yes we did push a change there (as we’re in beta we’re still refining the API). Having said that we’ll look into fixing this on our end so that it doesn’t conflict with names you define. Sorry about that
Hi @emmanuel, the issue with properties.element_id is fixed but it now looks like we’re seeing another regression:
Looks like any “Dropdown” field type, when used in an Element Action, is returning “undefined”, though it is actually defined. Only seems to affect Dropdown fields in Actions, Dropdown fields in element properties are still working fine.
Edit: To explain the demo, I have an element properties field of type Dropdown named foo. Then I have an action, with a field of type Dropdown named bar.
In function update, doing:
console.log(properties.foo)
returns the selected dropdown string. However in function action, doing:
console.log(properties.bar)
returns undefined, when it should return the dropdown string.