Prerequisites
What problem is your feature request going to solve? Please describe.
By enabling us to pull dynamic data to populate the Button ID (Button Widget) and/or all widgets attributes, we can dynamically populate those fields with data from custom fields so we can trigger different actions like custom popups (for the upcoming E Pro feature), modals, off-canvas or even custom styles for each element.
Describe the solution you'd like
-
Add the Dynamic tag to the button ID so each page with the same template can leverage the use of the same button for N actions or styles depending on what page the user is and the information we input on each page's custom field.
-
Add the Dynamic tag to all the widgets, sections and columns so we can populate that field with dynamic attributes that can be leveraged to change styles, trigger action scripts and all sorts of interactions based on a custom field of the page we are.
Describe alternatives you've considered
Doing the other way around, like triggering actions or making style changes based on a static information, but this way you limit the interactivity and usability of these functionalities. It can be simpler to do like I'm proposing and also less resource intensive since we won't need to make multiple templates and workarounds to achieve the same result.
Additional context
I was trying to open popups from the same layout and find that functionality would greatly improve and simplify what I was trying to do. In the end I had no viable solution without too much workarounds.
Prerequisites
What problem is your feature request going to solve? Please describe.
By enabling us to pull dynamic data to populate the Button ID (Button Widget) and/or all widgets attributes, we can dynamically populate those fields with data from custom fields so we can trigger different actions like custom popups (for the upcoming E Pro feature), modals, off-canvas or even custom styles for each element.
Describe the solution you'd like
Add the Dynamic tag to the button ID so each page with the same template can leverage the use of the same button for N actions or styles depending on what page the user is and the information we input on each page's custom field.
Add the Dynamic tag to all the widgets, sections and columns so we can populate that field with dynamic attributes that can be leveraged to change styles, trigger action scripts and all sorts of interactions based on a custom field of the page we are.
Describe alternatives you've considered
Doing the other way around, like triggering actions or making style changes based on a static information, but this way you limit the interactivity and usability of these functionalities. It can be simpler to do like I'm proposing and also less resource intensive since we won't need to make multiple templates and workarounds to achieve the same result.
Additional context
I was trying to open popups from the same layout and find that functionality would greatly improve and simplify what I was trying to do. In the end I had no viable solution without too much workarounds.