🆙Changelog

Reminder: Changes here will affect only new apps created with the template. If you have already started your app using the template, you will not receive these updates in your existing apps.

If you have already started your app using the template, you will not automatically receive these updates into your existing app. You will need to manually bring them over into your existing apps if you deem them necessary. I have tried to provide enough explanation below to make this simple but please let me know if you need help.

4th July 2024

• Added Replicate API call for generating music Replicate is an excellent service that lets you run all kinds of open source AI models, including your own, via an API. I added in a simple API call to one of the open source models which generates music from a prompt. You will need to add your own Replicate private key in the appropriate place. There are two API calls, one to create a prediction and one to get a prediction. Creating a prediction starts the model running based on the prompt you give it. You then need to check back periodically to see if your prediction has finished running, this is when you use get a prediction. You can replace the model ID with any of the open source Replicate models, but you will also need to update the JSON body so you are sending through the right parameters e.g. if you're creating an image, it won't need a duration.

  

  In the example I've created, I first run a backend workflow replicate - generate music which runs the Create a prediction API call.

  

  The workflow then schedules another backend workflow replicate - check prediction to run in 10 seconds time. This workflow uses the Get a prediction API call to check if the AI generation is complete. If not, it schedules itself to run again in 10 seconds time. This will continue until it returns a response from Replicate.

  

7th June 2024

• Fixed signup issue where the "require email confirmation" functionality was not working correctly. I was made aware that switching on "require email confirmation" on specific roles in the OS - User Roles option set was not working correctly. Users who signed up were receiving the confirmation email but somehow their email address was being automatically confirmed without them doing anything. After investigating I discovered this was likely a timing issue with the way the initial signup workflow was running, and I eventually ended up refactoring the entire signup workflow to make it more robust. If you are running into this issue please watch this video to see how to update your signup/login workflows.

• Simplified the menu option sets by consolidating the OS admin dashboard tabs into the main OS dashboard tabs option set. This should make it simpler to create multiple dashboards. All the sidebar menus now run off one option set and subtabs run off a second option set. There is a new option set called OS - App Locations which is a list of the menu locations within the app, this is used to decide which tabs to show where. For existing apps I wouldn't recommend trying to bring this change into your app, it's not necessary.

3rd May 2024

• Fixed missing plugin actions (Toast plugin) on accounts + settings reusable Weirdly a few actions related to Toast (confirmation notifications plugin) had gone missing in the workflows so they were showing this... I have deleted and replaced these actions with the correct Toast action. If you need to fix an older version, simply delete any missing actions and add in a Toast action (or copy and paste from elsewhere), similar to below.

26th April 2024

• Fixed a bug on the email confirmation page The confirmation page is where users are sent if their role requires email confirmation but they have not yet confirmed their email by clicking the link in the automated email. I realised there was an error in one of the workflows on the page which was supposed to trigger when they had confirmed their email and either send the user to onboarding or to their homepage. The conditional below should say is empty rather than isn't empty (this is checking if the user has completed all their onboarding steps). I also added another conditional to the trigger for this entire workflow to say that if the current user's role doesn't require email confirmation, do the same page redirect. This is just in case a user accidentally lands on this page when they shouldn't be there.

11th April 2024

• Made sure you cannot invite a user without filling out the email and role fields In the UI: Section - Account + Billing, Donnie spotted a bug that allowed you to click the invite button even if you hadn't filled in the email field and role dropdown. I added a conditional on the button to make it not clickable if either were empty.
• Fixed a bug which was redirecting logged out users to the email confirmation page There was a workflow in the 🖼️ Layout: Dashboard header reusable which would redirect users to the confirmation page if their email address had not been confirmed (i.e. they had not clicked the link in the confirmation email). This was incorrectly redirecting logged out users to the confirmation page. There was also no workflow generally redirecting logged out users away from the dashboard. To fix this I updated the redirect workflow to only occur when the user is logged in, and added another workflow to redirect the user to auth if they are logged out. For older versions of the boilerplate you will need to do the same: 1) In the Layout: Dashboard Header reusable on you will need to add "and the current user is logged in" to this workflow trigger's conditional. This will prevent it redirecting to that page. 2) You should also add another workflow "When user is logged out" with an action "Go to page... auth", which will then correctly redirect logged out users to the auth page.

  

  Step 1: Update this workflow

  

  Step 2: Add this workflow

2nd April 2024

• Simplified the demo mode to make it less work to remove!

  Unfortunately to provide a Bubble template it must offer a demo preview mode. Obviously I don't want random people creating things in the database or making changes to test credentials. So there is now one user in the database - [e-mail] - and a "demo login" button on the landing page which logs the tester in as [e-mail]. There are a load of conditionals on various buttons which make them not clickable if the current user's email is [e-mail]. You can remove these conditionals if you want but the point is you don't need to if you don't want to, it shouldn't affect your app (unless you have a user with the email [e-mail]). See the updated READ ME FIRST for more information.

23rd March 2024

• Moved the right sidebar into the table reusable elements rather than a shared one on the dashboard In the Table reusable elements (Classic rows, Image grid, Coloured grid, Calendar) I have moved the right sidebar to be within the reusable element itself. This makes it much less fiddly to customise the sidebar to show the information you need for each table. Previously the right sidebar was hidden on the dashboard and triggered with a URL parameter. This added extra complexity but at the time I thought it was the only way to do a full height sidebar. Thanks to some custom CSS it is now within the reusable itself.