Hello fellow Bubblers!
After 4 years of bubbling and endless years of conventional coding I just released my first Bubble Plugin… a booking calendar.
Why a Booking Calendar?
Because I was searching for my main Bubble application a booking calendar myself. I did not find any suitable one within the existing Plugins and was not happy with the reusable approach.
Why a Plugin?
Because I wanted to try out Bubble Plugin development and I think others can also benefit from the work I have done.
More Information?
Demo: Booking Calendar Demo
Editor: Booking Calendar Editor
Plugin page: Booking Calendar Plugin
Do not hesitate to ask questions. I am happy to take feedback. Also improvement ideas or feature requests are welcome. Nevertheless I made the Plugin simple by intention and do not want to overload it. It shall be very easy to integrate into your application.
You may contact me through the forum or via email.
Best, Andreas
5 Likes
Hello Andreas,
I just bought your plugin booking calendar,
it is great but may be I bought it to quickly… This plugin is only to show the booking or can we do a new book too from your plug in?
Thanks
Hi Raphael,
thanks for buying my booking calendar plugin.
You are right, the main functionality of the plugin is to show bookings & blockers. The only functionality which supports creating & editing bookings is through events (new button & context menu). The reason is that this supports maximum flexibility, since I don’t know, which data people would like to store with a booking.
The implementation of this functionality is straight forward. To create a new booking:
1.) Enhance the “Booking” data type to your needs (e.g. address, phone#…)
2.) Register for the “Button event” in your workflow (see demo)
3.) Show a dialog gathering all the data for a booking
4.) Store the booking
5.) It will automatically show-up in the calendar
The implementation for editing a booking is very similar.
I hope this helps. Let me know, if you have additional questions.
Best
Andreas
Hi Bubblers,
just want to let you know, that I have updated the plug-in to support Bubble‘s new responsive engine. Together with some some small bug-fixes, I made the show/hide feature of the custom button dynamic.
Check it out.
Best
Andreas
1 Like
Hi Andreas,
I am having trouble setting it up. I have an Airtable database providing the “Jobs” to be shown on the calendar. For the “blocked dates” I want those attached to the User, since they will be able to set their own blocked dates to show when they cannot work. When I set the “Blocks data source” to Current User’s blockedDates (which is in the Bubble database as a LIST of date-ranges) it shows this error. Any ideas?
Hi ajlowndes,
the type of “Blocks data source” needs to correspond to the type defined in “Type of blocks”. In your case please change “Type of blocks” to “date range”. That should already do the trick.
Let me know, if it worked.
Best
Andreas
Hi thanks for the prompt reply. No it didn’t work - please see the attached:
Hi ajlowndes,
I apologize for the inconvenience.
I checked the Plugin and found out, that as of now “Type of bookings” & “Type of blocks” have to be the same object type and cannot be simple types as for instance “data range”. If you look at my example, both are of type “Booking”.
In your case I suggest, you use “Jobs” for the booking & blocking dates. Just add a list of Jobs to your user and only use the fields for start & end of the jobs in the case of blocks.
Best,
Andreas
Hi ajlowndes,
I just released a new version of the Plugin (1.4.2). In the new version you can specify a separate object type for blockers. That means you do not have to use Jobs for blockers, but could create an object called Block with just 2 date fields (start & end) and add a list of Blocks to the User object.
Best
Andreas
Great! I wanted to play with that but I’m having a bit of trouble showing the events on the calendar. I’m getting this error:
Is it possible to specify the start/end fields when using an API like Airtable to pull in the “jobs” data? I feel like your implementation heavily relies on the data being in the Bubble database natively and in a very specific format.
Other changes to make sure are there (if you are going to update the plugin):
specify which field in data source is the “event Caption” or title
specify start of week (I am setting Monday but you have Sunday by default and it doesn’t seem to be able to be changed)
There is a certain way in which you can build Plugins for Bubble. The way on how to expose parameters is constrained by Bubble. I am doing it in the Bubble suggested way. If that does not work for Airtable then there is not much I can do. If “type of bookings” has the right format (2 attributes of type date) there should appear 2 additional fields to enter start & end date of the booking. Also 2 fields to enter caption of the booking.
I am sure you checked the demo workspace: Your Bubble app
The start of the week is derived from the locale you provide in the parameters (last one). I use “de” myself and the calendar starts with Monday.
Best
Andreas
Thanks so much Andreas, that understanding helps heaps. I’ll check it out.
