I had been using the orchestra plugin by @vini_brito since it’s release and had no issues with it. Recently this plugin was acquired by @ZeroqodeSupport and it is now not functional and causes the application to crash. I have submitted an email to zeroqode support, but just wanting to give a heads up to anybody that uses it in live apps, I believe @chad@zelus_pudding I’ve seen on the showcase thread the kind words you expressed as appreciation to @vini_brito for all he has done for the community through his plugins and suspect you both may be using the plugin in your apps, and curious if you are experiencing any issues as well.
Specifically, the initialize musicians workflow action causes the app to crash.
Yes…takes about 5 minutes for it to show that but that is the error reported via the popup.
I’ve continued to dig deeper into this and what I am seeing now is that my repeating group, which is tied to a list of numbers, which is set to 0 on page load, so the repeating group (which has the musicians element) is visible but without any content, that is when I have the issue. If I make it so the default value of list of numbers is 1, and so therefore the repeating group has content, then the issue does not occurr.
I’ve tried to set a condition onto the workflow trigger for ‘when musicians is revealed’ to run only when the repeating group list is greater than or equal to 1 but when that repeating group starts at 0, so no content, the issue persists.
So it seems that the issue most likely is on my side, but the workarounds I need to do leave open some ideas on how the plugin could be improved.
What I’ve done to overcome this issue and still get all the other functionality I need is that on the repeating group (that has the musicians element) I placed a conditional.
So, in this setup it seems like the musicians element is not revealed until my count is greater than or equal to 1, and that my RG becomes visible. I believe the conditions on the trigger event for when a musicians is revealed are not followed for some reason.
The above screen shot with condition on the trigger event doesn’t work and the issue persists. But the repeating group not visible until has content works.
I think my scoper tool kind of mimics what the Orchestra plugin does but acts a little differently. I can make it work just like Orchestra though if needed. Let me know if it works for your use-case and if i not I can modify it like so. It’s able to return strings for now, but I can make them custom objects.
After thorough review, it wouldn’t do justice in terms of behaving like Orchestra, so I had to modify and add onto it to work like so. Since my reply earlier, I have been working on the plugin below and to make sure it worked.
There you go. I have turned Scoper into a dedicated plugin and it also works just like Orchestra with some added benefits.
I also rewrote the code so it all should work as expected. Not to mention it’s 100% free, and works as intended.
Like scoper (now called Energy Pods):
Trigger events/conditions on ANYTHING
Listen to any input
Do anything based on the input
Send dynamic data to each pod
Spawn an Energy Pod Listener
See when a pod (or cell ideally) is loaded/visible
Trigger the Energy pod from an energizer (1, multiple, or all)
No trackers
I think there is more, but I am tired haha.
Adding later: Sending data & trigger to Energizer element from Pod.
I need to try this out but I’m thinking you could do pretty similar by adding a js_to_bubble element inside the rg’s cell with an id that has the cell index appended,
Then outside have a run js action, using rg_format as text to form up some js to call each bubble_fn.
That bubble function can run an event and whala almost vanilla bubble orchestra (let’s be honest @mishav toolbox plugin is practically a native plugin at this stage, every app has it)
Sounds like a lot of work - why I made Energizer an independent plugin. It’s pretty powerful IMO and can turn your app into a dynamic machine (in terms of conditionals, workflows, RG data/manipulation, etc).
I used to use the Orchestra plugin quite a lot, and it always worked great… but I always found using it to be needlessly overly complicated for what it is.
More recently, I haven’t found a single thing that I could do with the Orchestra plugin that I can’t do more easily, more cleanly, and with less work (plus with more control), by using the Toolbox JavaScript to Bubble element and some simple JavaScript (even involving complex nested RG and nested RE situations).
@boston85719 we heavily use the orchestra plugin in one of our apps and we’ve noticed this issue already last year. This is not new so I’m positive this may not be zeroqode’s fault.
As what you’ve said, the cause of the issue is having 0 as the default number of cells in an RG. We have the same structure - we also use list of numbers.
The solution is to just pretty much set the default to 1.
This suddenly happened for no reason, similar to you.
We’ve recently acquired the plugin and wish to clarify that in the latest 1.3.0 version, there have been no modifications to the plugin code itself—only the general description has been updated.
Our development team is currently conducting an in-depth review of the plugin’s roadmap and strategizing for future updates. We will keep you informed about any developments or forthcoming enhancements concerning the plugin.
Regarding the error mentioned by @boston85719, it indeed relates to an issue with setting 0 as the default number of cells in an RG as mentioned by the @ntabs . We have already passed this concern onto our development team for further investigation and resolution.
Once again, thank you. If you have any further questions or require assistance with any of our plugins, please let us know.
We wanted to follow up on the problem previously mentioned by @boston85719 and share further insights from our development team.
To effectively address the error, it’s crucial to adjust the triggering of the “Initialize musicians” action. The issue occurred because the action was set to trigger upon “page is loaded.” However, it should be configured to activate at the plugin’s “Revealed” event: Screenshot by Lightshot.
For further clarity, I encourage you to visit our demo page, where you can see a live example of the configuration: Orchestra-test | Bubble Editor
We are continuously working to improve the plugin, so if you have any questions, concerns, or suggestions, please do not hesitate to share them. Your feedback is invaluable and we are eager to assist.
Thank you all once again. Wishing you a fantastic week ahead!
I’m sorry but from what I experienced the issue occurred because the initialize musicians was triggered when the repeating group the musicians element was placed into had a count of 0 items. When I was testing and debugging to resolve I found this out the long way. During that long debugging session I did have the epiphany to try to initialize the musicians on the plugins revealed event, which is actually my preferred way of using the plugin, and the way I originally had it configured, but because the RG items count was 0, the musicians element was not revealed, and so couldn’t be initialized, the same way it couldn’t have been initialized on page load because at that time the musicians element was also not visible.
The test page you provided does not have a repeating group that is empty. I would suggest attempting to try the trigger of musicians is revealed to run the initialize musicians with a repeating group that is empty. That might help the team improve the app and effectively address the error with a solid understanding of what the issue was.
Thank you for your detailed feedback and for taking the time to describe the difficulties you encountered.
We are continuously seeking ways to enhance our plugins and ensure they effectively meet user needs. We will specifically explore methods to handle the initialization process when the repeating group is empty.
We will keep you informed of any progress in this area and aim to include potential improvements in future updates. Please feel free to share any more suggestions or reach out if you need further assistance.
Thank you once again for your valuable contribution and for helping us improve our plugin.
- why I made Energizer an independent plugin. It’s pretty powerful IMO and can turn your app into a dynamic machine (in terms of conditionals, workflows, RG data/manipulation, etc).
