I’ve noticed that the Orchesta plugin doesn’t work the first time it’s event is called (e.g., a button click). The user has to click the button twice to get it to work. Then after that, it works with each button click.
I’ve had to come up with terrible hacks to address this. I have two questions:
Anyone have an elegant solution?
Why does bubble not natively support the functionality of triggering actions within a repeating groups cell(s) from outside of the repeating group? This seems like table stakes functionality.
Hey @bryan.holmes ,
Thank you for contacting us.
Unfortunately, this behavior is dictated by Bubble itself: the editor will show the “Initialize musicians” action even when it doesn’t have access to the corresponding elements (e.g., when they’re inside a Repeating Group).
As plugin developers, we don’t have control over this aspect of the Bubble editor.
That said, we do acknowledge it’s not ideal — especially since it can consume unnecessary app resources and complicate your workflow.
Our current recommendation:
You can use the “Musicians revealed” event, which reliably fires when Musician elements become visible/rendered on the page. At that point, you can trigger “Initialize musicians” safely, ensuring that the class is applied only when the elements are accessible.
Right now, this is the only reliable approach available within Bubble’s constraints.
Please let us know if you’d like help implementing this flow — we’re happy to assist!
Best Regards,
Zeroqode Support Team
