We appreciate your innovative approach to using the plugin with Xano API and avoiding the Bubble database.
Please do keep us informed about your use case and the solutions you implement. We’re very interested in how our users creatively apply our plugins to their unique scenarios.
If any other questions or needs arise related to the plugin, don’t hesitate to get in touch. We’re always here and happy to assist.
Hello @befi ,
Thank you for your interest in our plugins.
The “refresh” happens due to the fact that on our page in the workflow, there is a loading element, we have added them since we have a large workflow, and the plugin needs more time to properly initialize and complete all actions. You can create your workflow without the load element if you don’t need the waiting time in between actions.
Please note that we provide general support for our plugins and do not offer consultancy or customization services.
We recommend reviewing the demo page for workflow examples and carefully reading the supporting documentation for successful plugin integration.
If you’re looking for a team to assist with customization, you can consider hiring Zeroqode. By sharing your project details and budget, one of our project managers will get back to you with an estimate.
Below are a few tips to help you when customizing the plugin:
Steps to Set Up the Flow:
Create a Custom State:
Set up a custom state (e.g., isDragging) on the element or on the page. This state will be used to track whether the dragging has started or not.
For example: isDragging (Boolean, default value = no).
Trigger the Drag Start:
In the workflow, when the drag starts, you want to change this custom state to yes (indicating that the element is being dragged).
Action: Element -> Set State -> isDragging = yes.
Change the Element’s Visibility:
Use the isDragging custom state to dynamically adjust the element’s size.
For example, when the isDragging state is yes, you can conditionally apply a smaller size to the element.
You can do this by setting conditional formatting on the element (e.g., When isDragging is yes, set width/height to 80%).
Add a Drag Event:
Use the drag event (provided by the Drag & Drop plugin) to trigger the workflow when dragging begins or ends.
When the drag ends, you can reset the isDragging state back to no, which will then reset the element’s size to its original state.
Example Workflow:
Start Dragging:
Action: Element -> Set State -> isDragging = yes.
Action: Change element’s size (e.g., decrease width or height by a percentage).
Stop Dragging (when drag ends):
Action: Element -> Set State -> isDragging = no.
Action: Reset element’s size to original dimensions.
The information we have sent you is only advice that may help you, but you are not obliged to follow it.
We do not help with customizing the plugin, there is documentation and a demo page for that. The Bubble community is very large, and we are sure you will be able to find the answer to your question by searching the Bubble forum or creating a separate thread with the question.
Running into a bug. When I have 0 items in the repeating group, and then I add one to the list, I get two items show up underneath the RG item saying “Drop Element” underneath the item.
Anyone else experienced this or know what’s going on?
Hi @simon.peacock,
Thank you for reaching out and for using our products.
We’re delighted to hear that everything is now working well. Please don’t hesitate to reach out if you need further help or assistance – we’re always happy to support you.
If you’re enjoying our plugin, we’d be so grateful if you could take a moment to rate it! You can head to the Plugins tab in the Bubble editor, search for the plugin by name, and leave the stars you think it deserves. Your feedback truly motivates us to keep improving.
I’m running into a visual bug with the Drag & Drop to Reorder RG plugin:
After I drop an item in its new position, it briefly jumps back to the old position and then jumps forward again to the correct new spot. This flicker happens on every single reorder.
I tested both save options:
“Use ‘Sync of sorting with DB’” enabled → jumps back
Custom workflow on “A Draggable RG Moved” → also jumps back
For a 70 USD plugin built exactly for this use case, a clean drag-and-drop without visual bouncing should be the baseline.
Previously, someone already flagged this, so we investigated the issue internally, and here’s what we found:
We were able to confirm that the blinking and jumping (or flickering) effect you’re seeing is caused natively by how Bubble handles DOM updates. Whenever the database is modified—which happens when the order is saved immediately after a drop—Bubble automatically refreshes the DOM to reflect the database change. That native refresh is exactly what creates the brief visual jump you are experiencing.
Because this behavior is tied directly to Bubble’s internal rendering and database synchronization process, it unfortunately cannot be eliminated from the plugin side.
To achieve a smooth drag-and-drop experience without the visual bouncing, the best workaround is to use the manual “saving to database with action” approach. Instead of updating the database immediately on every move (which triggers the Bubble DOM refresh each time), you can let the user reorder the list visually first, and then commit the final order to the database via a specific action (such as a “Save order” button). This bypasses the continuous DOM refreshes during the sorting interaction.
Please let me know if you need any help setting up the manual sync workflow!
We have just released an update for the Drag & Drop to Reorder RG plugin, version 1.53.0. This update includes a significant cleanup of the codebase and fixes a known behavior issue.
Here is a breakdown of what’s included in this version:
Code Refactoring: We’ve optimized the plugin’s performance while maintaining all existing functionality. This includes:
Removal of duplicate styles to streamline loading.
jQuery optimization by switching to native methods instead of standard code blocks.
Cleanup of unused code to reduce bloat.
Specific optimization for mobile devices to ensure smoother interactions on touch screens.
Bug Fix: We’ve resolved the long-standing issue where elements would “jump” unexpectedly while being dragged.
New Field Added: You will now see a field called Use ‘Sync of sorting with DB’. We added this to allow users to keep the old correction method if their specific workflow requires it.
To apply these changes, head over to the Plugins tab in your Bubble editor, locate the Drag & Drop to Reorder RG plugin, and select version 1.53.0.
I highly recommend reviewing our official documentation and checking the demo editor to see how the updated logic performs. These resources are the best place to start if you have questions about the new settings or mobile behavior.
If you encounter any issues with responsiveness or logic after updating, please let us know.
Hello, I am having difficulty with the handle movement on mobile devices. It works well on desktop, but the drag and drop does not work on mobile. I tested it on the demo site as well.
Thanks for providing those specifics! Knowing you’re using Safari on an iPhone 15 Pro with iOS 26 is really helpful for our team to pin down the environment.
I’ve officially confirmed the issue on our end as well—the drag-and-drop handles aren’t responding as they should on mobile devices. I’ve already passed all the details and your feedback directly to our developers so they can start working on a fix.
We’ll keep a close eye on this and I’ll make sure to update you as soon as I have news from the dev team regarding a patch or a plugin update.
Thanks for your patience while we get this sorted!
I have an update from our development team regarding the handle movement on mobile.
After looking into the core library that powers the Drag & Drop to Reorder RG plugin, our devs confirmed that handle-based dragging is unfortunately not supported by the library for mobile devices. Because this limitation exists at the library level, we won’t be able to implement this specific functionality for mobile at this time.
Thank you for your understanding and for helping us look into this.
