Today I saw that the limitation of 200 records in the database, in the free plan, has disappeared. Has this restriction been removed?
3 Likes
Thank you for engaging with your community and the transparency.
@josh Could you please improve the quality of the agency job requests.
Many requests are just plain junk or they have 2-3 sentences of description which is obviously useless.
With the current agency work request implementation it seems to me that Bubble does not have any respect to its agency partners’ time.
@josh The data protection compliance issue remain for many of us. When will we be able to select EU hosting location?
ps. SOC2 is good news for us and many other companies.
2 Likes
You can technically do this today, but it has to be a dedicated server w/ Bubble.
Thanks @josh for the update…couple of requests/ideas
Can you switch the default behavior to show templates we created before templates we purchased? 99% of the time that I look at templates section it is to find ones that I built rather than ones I’ve purchased…I know my case may be different than others as I build and sell templates, so perhaps a toggle to select which we’d rather see first.
This is great! One other idea for improvement related to URLs and specifically SEO. Please provide a way to still use the page content type, but to send in a ‘go to page’ action the ability to send more path items; additionally a way to make ‘send data’ optional just like for our custom workflow trigger and backend workflow parameters.
For example, if I have a page content type of ‘product’ and I want to use the same page for my product search as I do for my product listing by simply having my URL go from myapp.com/product to mayapp.com/product/cool-shoes, currently by the fact that a page with content type is forced to send data, it is a bit cumbersome to make it so the page URL on navigation could be myapp.com/product in the event I want to navigate the user for the search function and not actually send a product to the page.
Additionally, the need to send data with more than just the data type entry. If we can use the send data input to add additional path items it would help. Yes, users who would be wanting to make use of such a feature would need to be understanding of how it works, but it could be something that Bubble automatically takes the first item in the path as the page content type thing, and any additional path items sent are just sent by Bubble.
For example 应用宝官网-全网最新最热手机应用游戏下载 could be sent with the send data on go to page navigation with the data to send being ‘store’/menu where ‘store’ is a dynamic value and /menu is just plain text…currently I have to use the link element to do this and it causes a poor UX in the fact that users who are already on the page for the particular store, the page has to reload to just change the path item of menu, because it is the link element and not the ‘go to page’ action.
I can do this currently but it requires me to not use the page content type, so it makes it less appealing because I can not use the ‘thing link’ operator to generate links for the store, because the workaround is no page content type and use the data to send in the go to page action as text only.
Another useful thing for both parameters and path items would be to enable the function to verify the entry in the database for the designated thing on URL extraction by the slug and not just the unique ID. Currently if you use the Get data from URL workflow action and indicate the type of data to be extracted, if you have the unique ID in the parameter or path item, Bubble will display the data entry just like it would if you set the page content type…however, if the page content type is not set, and the parameter or path item is the slug of the entry, Bubble doesn’t recognize the entry. Currently when the page content type is set, if the slug is not set on the thing, and the backup field for URL is left empty, then the unique ID is used as the path; this indicates Bubble is able to differentiate the database entry from either the unique ID or the slug…it would be great if this was enable for our own extraction in the dynamic expression.
Currently, either of the below dynamic expressions will not return a result if the value is the slug of a blog post
If, however, it is the unique id of the blog post it will return a result.
It would be fantastic and provide an ENORMOUS boost to SEO benefits from URL structure and data ‘storage’ & passing values through the URL.
3 Likes
allow elements to be visible in builder, even when set to invisible on page load plz 
1 Like
Hi @josh , always happy to read the monthly community update!
I have a question for you: do you plan to work on improving the backend for bulk edit / delete? Your answer will guide in my choice to connect to an external database or keep using Bubble’s database. Clearly, option 2 would be my preferred choice
Thanks!
i make a databse field called “delete, yes/no”, then when i want to delete something, a make a change to that field to “yes”.
in the backend there is a database trigger of “when cur things delete is yes” it deletes the thing
then for displaying information, you display things that are “delete = no” and you get a nice responsiv apperence as if things are being deleted right away.
This sounds like this would cripple your app’s capacity if you set a bunch of things to “yes”…
That’s what I think also because the issue is with bulk editing or bulk deleting. I’m talking here about 10k+ items.
Yea you can keep the yes/no field like @ksplinter007 suggested so on the front end things look like they instantly were deleted, but don’t do the database trigger because that will fail very quickly with large number of things.
Instead set that yes/no on all your Things, but then have some slow recursive workflow delete them one by one kind of like “garbage collection”
1 Like
Thanks I will probably try this before moving to a more robust solution like Xano or Supabase! It’s still a lot of bulk editing so I’m not sure it’s going to work but worth the try
i dont see why it would effect capacity? maybe i just dont understand that.
changing a list of things to “delete = yes” doesnt really seem to be that big of an issue. and its just a simple yes/no field.
then if your worried about backend capacity you could set it up where it looks for the first thing that is “delete yes” and delete it, then find the next thing that is delete yes, and delete it. and so on. but i find that a database trigger works the best.
i didnt read your entire post.
i have not seen database trigger fail. but yes something like "when list of things delete = yes >0, delete list of things with delete yes, then do a search for delete things thats yes, only when delete things is yes is >0.
that way if the first delete doesnt find everything, it will do another search and delete the next batch
Data api is faster for bulk editing