I have a query about the Air Date/Time Picker. I emailed @seanhoots about it since it is in relation to the Air Calendar plugin, to which I just subscribed, but thought I would also ask here in case I can avoid Sean some support work.
I discovered that enabling the āauto positionā checkbox causes chrome to throw a console error iFits is not defined at runtime when the picker is clicked. Subsequently executed JS on the page starts acting wonky as a result of this error.
The likely culprit is on line 406 in the āupdateā function code of the plugin)
406 if (!iFits) {
ā¦
It looks like there is a loop below that which tests the placement of the picker window in various positions and sets iFitsto true if it a position is valid and āfitsā, however it looks like the variable iFitsis not explicitly defined anywhere inside the update function and so when it is tested on 406 it is undefined and throws this error.
Hi,
Did you ever get an answer on this matter? I have the same kind of general error when clicking the pickers in reusable popups. It doesnāt seem to prevent my app from working, but itās weird to get a bug alert under normal operationsā¦ Thx!
Plus, I wonder if it could be linked to another problem I havenāt seen in any posts yet: Whenever I use the āblock datesā feature in such reusable popups (with a thing listing dates picked from an air date/time picker on another page), the app stops working ā with a slow progress bar appearing at the top of the browserās preview page but no other error showing in the debugger.
This happens in Chrome as well as in Edge. Iām new to bubble and Iām not proficient at all in coding, so it my be my building of the app thatās causing the problem, but I wonder if anyone has encountered the same issue?
Thatās too badā¦ And it points out a general issue I have in my evaluation of Bubble: itās nice that the community provides a lot of plugins (although with no trial offer for premiumsā¦), but it seems that an app can easily become completely dependant on them, with no assurance at all that theyāll remain functional in the long run. And itās kind of a big turn-off: itās probably safer to build with bubble-made components only, but then you have to give up a lot of cool or very useful featuresā¦ I mean, although itās annoying, I donāt mind a broken saved-game due to an outdated add-on in my personal life, but thatās not something I could afford with a professional appā¦ So, a lot of thinking ahead before bringing my company to bubbleā¦ Anyway, thanks a lot for your feedback!
It is a valid concern that hundreds of plugins are developed by anybody with the tech skills but no assurance of long-term support. As far as I can tell, Bubble is doing nothing to protect its community.
Is there any way to make the output of the time zone value entered in Date be displayed in 24 decimal instead of 12 decimal?
Is there any way to make the output of the time zone value entered in Date be displayed in 24 decimal instead of 12 decimal? (The value input itself should be in 24 decimal as shown in the picture.
My professional users will be able to schedule their session by time, day and session. So their clients need to be able to see the appointments by week in order to book an appointment.
So is it possible to display the calendar by week or to display the first of the week on a specific date so that the client can see the availability of the rest of the week?
So is it possible to apply the Availability data to all weeks?
Iām afraid that the current plugin functionality doesnāt provide such functionality. Sorry for the inconvenience.
Kindly note that as it is a free plugin, with available source code, you can adjust it considering the requirements of your project.
Hope it helps. In case any other plugin-related questions will appear, please let us know.
Could you please share your case conditions (screenshots and/or screencasts of your setup - workflows, plugin settings ) on which you get such a bug?
That will help us to identify the possible cause of your issue.
Weāve made a small bugfix for the issue with placeholder fonts weighting.
Please upgrade the plugin to the latest version (3.7.0 - font-weight displaying fix), refresh the application, and give it a try.
In case there will be any other plugin-related questions, please let us know, we will be glad to help .