Hey, Bubblers!
Our Digishop has just received a total overhaul from our development team. Weāve optimized workflows and completely rebuilt the design from scratch. Now it looks very stylish and stylish and modern
Weāve also updated the template to the new Bubble Responsive Engine. Check it out here:
Digishop is a responsive ready-made template built without code. This app template is a marketplace for selling digital goods. It can be adapted also for selling physical items. Digishop no-code template allows listing items from other sellers and managing customer-to-seller payments, while the store keeps the commission.
Sure, thing. Perhaps, itās not the perfect match for your requirement but can be used as a good base for the app you want to develop. We would like to suggest you test the Web Demo, to see if this template satisfies your needs before purchasing. Any modifications youād like to do - totally possible later on.
Hi, Iām considering buying your Digishop template. But I have a couple questions. Watching the video I noticed the Add a Book 1 page setup (really nice by the way)
1.) What is the Link area for and how does a user upload their book (And also download it - I tried that in the demo and it would not let me download)? Or should we Not allow the seller to upload a book because that could cause a lot of Data Storage problems? In terms of cost. Is the link to a google drive saved digital item?
2.) How do I change my Owners (meaning the owner of the marketplace) Commision of every sale? And also alter what the sellers get?
Link Area is used to indicate the link to the book that youāve uploaded to an online storage. If you use a third-party online platform storage to store the sold product itself - that would not cause many problems for the applicationās internal database, as it will store not much data in fact (only description). As for the safety of a Google drive link or any other platform, weāre afraid we can not provide much guidance, as it does not relate to our competence. Sorry about that. The best option would be to search for a platform that would correspond to your project requirements.
The commission value is applied to all transactions made through the marketplace. To change the value, please access the admin dashboard: Screenshot by LightshotScreenshot by Lightshot
The seller gets the amount on which the commission is already applied.
Hope this answers your questions. Please let us know if there is anything else that we can help with about our template.
How do I add books? I tried but Iām still in Development. Trying to āAdd a bookā leads to āConnect your Stripe Accountā and then leads to this Error Message - Sorry, there was an issue connecting with Stripe, please try again later. (invalid_grant) ā¦ I need to be able to add books.
Iām using the Digishop template and Iām trying to set up the admin login security properly. Stripe is requiring security measures on the admin dashboard login, including locking the account after 10 or fewer failed login attempts, so Iām trying to understand whether Digishop already supports this flow and how it is intended to be configured.con-one.crisp
Here is my situation:
In the Users data type, I can see fields such as failed_count, is_locked, and is_admin, so it looks like the template may already include a built-in login failure / lock mechanism.
I removed the original Digishop admin login form and replaced it with a normal login form using the Log the user in action on my sign-in page.
My admin user exists correctly in the database, with is_admin = yes, is_locked = no, and failed_count = 9 during testing.
On the sign-in page, the Login button workflow is pointing to the correct email and password inputs, so the form itself appears connected correctly.
What I expected:
If I enter the correct admin email and a wrong password, I expected the failed login attempt to be counted, and once the threshold is reached, the account should become locked.forum.bubble+1
What is happening instead:
The login fails as expected when I enter the wrong password, but failed_count does not increase in the database.
I also tried checking Bubble debug mode, but I could not get a useful workflow error trace from the failed login flow, so Iām not sure whether the Digishop template handles the failure in another place, or whether the built-in flow is no longer connected after replacing the original admin login form.manual.bubble
My questions are:
Does Digishop already include a built-in admin failed-login counter / lock flow?
If yes, which exact workflow or reusable element handles it?
If I replace the original admin login form with a standard Log the user in action, do I also need to reconnect some additional Digishop workflow manually?
Is the intended failed-login handling based on Bubbleās An unhandled error occurs event and INVALID_LOGIN_CREDENTIALS, or is Digishop using a different method internally?forum.bubble
Also, if the demo users or demo login flow are related to this behavior, please let me know whether they should remain during setup or whether they can be safely removed before configuring the admin security flow.docs.zeroqode
Thanks ā Iām mainly trying to make sure I implement the admin login in the way Digishop expects, instead of rebuilding the whole security flow from scratch.
Iām not very experienced with Bubble yet, so if I misunderstood how the template is designed, please let me know.
Please note that the Digishop template is no longer owned or maintained by Zeroqode - it has been transferred to the @rapidevelopers.
Because of this, we do not have access to the internal setup or workflows of the current template version.
You can reach out directly to the Rapid Dev support team at support@rapidevelopers.com, and they should be able to assist you promptly with these questions.
Once you donāt need the demo users functionality, please be sure to remove the āDemo Loginā button functionality, as well as the demo users from database. For guidance, please see documentation here
Hope this helps. If there are any additional questions about the default template setup, please send us an email to support@rapidevelopers.com, and we will gladly help
Thank you very much for the clarification and detailed response.
I now understand that the failed_count, is_locked, and is_admin fields
were not part of the original DigiShop template ā I must have added them
myself during earlier customization. That clears up my confusion.
I also appreciate the reminder about removing the Demo Login button and
demo users before going live. I will follow the setup guide you shared
and clean those up before launch.
