I have given a condition to disable the loading but it doesn’t really work. Even tried changing the loading time to 0 but no luck. Please fix this. Thank you.
Have provided the image to the condition. I only want the skeleton loader to work when page is view for the first time or when its reloaded not when the data is already displayed.
Hello @shravan,
Thank you for reaching out to us.
The plugin offers two actions that enable you to disable or enable the animated loading on your page. You can trigger the “Stop preloader” action in your workflow once the data is displayed, as per your use case.
If there are any areas you believe could be improved, could you please specify what exactly in the plugin you would like to see enhanced or added? We greatly value your feedback and are eager to consider your suggestions.
Thank you once again, and we look forward to your reply. 
Best regards,
Stefan
I wanted to disable the skeleton reload based on the conditions I give it. May I know why it doesn’t work that way? I also tried through workflow to disable the loader when the data is already displayed (run the workflow when condition is true). But it still reloads as the page is not displayed through state it’s displayed through url. (Go to page …and send parameters) Workflow.
Hello @shravan,
Thank you for your message and explanations.
From what I understand, you are looking to start and stop the preloader conditionals. I’ve noted your request and have already forwarded it to our development team to explore this possibility. I will keep you updated as soon as we have more information on this matter.
At present, the ‘Enabled’ checkbox is designed to control whether the element activates on page load and is not set up for use with conditional triggers.
Thank you for your collaboration and patience.
Wishing you a fantastic week ahead!
Best regards,
Stefan
Hello @shravan,
I hope this message finds you well.
I’m writing to address your inquiry about transitioning the Skeleton preloader from conditional triggers. After consulting with our development team, we’ve devised a straightforward solution for you.
You can establish a “isLoading” state of type yes/no, which will control the start/stop of the effect via your conditionals(img).
In your workflow, add two “Do when condition is true” events that will automatically trigger or halt the skeleton effect when the “isLoading” state changes. (img)
Additionally, I’ve set up a test page (link) where you can see this implementation in action. Feel free to test it and replicate the setup(img).
Could you please review this and let us know if everything functions as expected?
On another note, I wanted to ask if you were the author of a recent review for our plugin. If so, I would like to kindly request if you could reconsider it. We’ve reviewed the conditions you mentioned and found they weren’t intended to stop the skeleton effect, and addressing this is very important to us.
Thank you for your cooperation and understanding. We eagerly await your response.
Best regards,
Stefan
Set state doesn’t work for me as I show the details page through (go to page workflow) which will reload the tab again. So I wanted to see if it will disable the loader when the repeating group is not loading as I show the details through api. Once the api is fetched it doesn’t need the preloader/skeleton loader. But in the current scenario we see the preloader even if the data is already fetched.
Hello @shravan,
Thank you for the message.
Could you please confirm that you’ve reviewed the message and test page I sent earlier? The workflow I described there, specifically using the “Do when condition is true” event, will certainly help you achieve the results you’re looking for. Just apply the condition you illustrated in your first image(img) to the event(img), and let us know how it goes.
Also, could I kindly ask you to reconsider your recent plugin review? As we previously discussed, the conditions you attempted to apply are not suitable for initiating or ending the skeleton effect.
We would greatly appreciate it if you could reevaluate your review.
Thank you once again, and I look forward to your response.
Best regards,
Stefan
Also found this bug in the errors section on preload. Let me know if this issue could be resolved. Thank you.
Hello @shravan,
Thank you for reaching out.
We’ve tried to test the plugin with different configuration but didn’t managed to find any issues as you described, could you please provide additional details such as screenshots and screencasts of your workflow and plugin element? Specifically, how did you configure the actions of the start/stop plugin in your app? Additionally, could you record a step-by-step video from the time you launch your page until you encounter the error you mentioned? This will help us better understand and address any possible problems.
Could you also confirm whether you’ve had a chance to review the test page I sent earlier? We are committed to assisting you with any problems, but we need more detailed feedback from you to proceed effectively.
Thanks again, and I look forward to your response.
Best regards,
Stefan
Here is the loom video https://www.loom.com/share/0b52f66e458b4de4a9eedca98496c391?sid=b8d3543b-659d-4670-9d16-256e79c79507 that you had requested for, I have explained how it behaves on the page load and also when data has already been fetched. Also showed how I have implemented it.
Regards
shravan
Hello @shravan,
Thanks for you message and the video.
Firstly, I’d like to kindly ask you again to reconsider the review you posted for the Plugin (link). As we’ve discussed previously, the conditions you were implementing were not designed to address the skeleton effect, and we are determined to help you resolve any difficulties you may face with our plugins.
From your video, it appears that the event “Do when gp status” isn’t being triggered, as the animation stops after 5 seconds, as configured in your setup(img). Could you please confirm this?
To further diagnose, could you record another video in step-by-step mode! to verify if the event is being triggered at all? If it’s not, it might indicate that the condition isn’t receiving the value you’ve assigned. I suggest trying a different state/value for the condition or double-checking your setup.
Also, please view this Loom video to see how the events are triggered instantly when the condition is modified, and stopping the skeleton effect at the same time. This demonstration uses the same test page as before.
Thank you for your attention to these details. Your cooperation is crucial to resolving this issue effectively.
Looking forward to your reply.
Best regards,
Stefan
That trigger is fine as it displays that element when other condition is met but the workflow to stop the loader is not working.
Hello @shravan,
Thank you for your message.
I’m sorry to hear that you’re still experiencing difficulties with setting up the action. To better understand the issue, could you please create another video in step-by-step mode and check every step so we can see exactly how each action affects the page? Additionally, consider increasing the duration of the Preloader time to more than 5 seconds (img) to prevent it from closing automatically. Could you also please check which Bubble version you are using, and whether you’re using the old responsive engine or the new one?
Thank you once again, and I am looking forward to your reply.
Best regards,
Stefan
Hello @shravan,
I hope this message finds you well.
I just wanted to follow up on my previous request for a step-by-step video demonstrating the setup of the action you’re having trouble with. This would greatly help us in diagnosing the exact issue and providing the right solution.
Also, could you confirm if you’ve had a chance to adjust the Preloader time as suggested? It’s important to ensure it doesn’t close prematurely during the process.
Lastly, please let me know which version of Bubble you are currently using and whether it’s the old or new responsive engine. This information is crucial for us to better understand the context of your setup.
Looking forward to your response so we can resolve this issue promptly.
Best regards,
Stefan