I think you are missing a āyā for the default formats?
I have this:
In the field it shows:
Iām using custom now anyway, but thought Iād let you know (and sorry if this was already mentioned)
And I have one request
Would it be possible to change the color of the placeholder? I have date pickers that are disabled based on a role. But a datepicker in the same RG could be marked to edit for the same role. In this situation it is not clear that one can be clicked and the other not (I have font color by default āgreyed outā and a condition to change the font to black when current userās edit is yes). But because the placeholder seems to stay grey, it doesnāt look editable.
Hope this makes sense
EDIT
I have been using this picker because it works much better responsively than the default, has more options and looks awesome! But there is one use case where I did not get this to work:
I have a repeating group with a date picker that stores a UNIX number using a plugin to convert the date to unix.
I cannot get this picker to work because I need ādo when value changesā which it seems this picker does not support. Instead it does things on āselectedā but I noticed in the log that it runs the workflow for all currently selected pickers in the entire RG.
Autobinding wouldnt work because I need the unix conversion. I could build an additional workflow triggered when the date was saved, but this is also too complex.
A button isnāt a great UX and had some other limitations.
Would something like ādo when value is changedā be possible or am I just using it wrong inside a RG?
EDIT2
I noticed something else, not sure if this is fixable.
When the date picker sits in a hidden group, a RG that is filtered on that date field will not use the initial content. It doesnāt see the picker because of the group that it sits in. The regular picker does work in this scenario.
Hi Sean
Just a quick question - the dynamic blocking greys / cuts out the blocked dates when using just a date selection - so works perfectly fine. But when using the dynamic dates blocking, the Air Date Picker still allows the blocked values to be chose in a range. Seems to be a small logic related issue? Ideally - if any one day is blocked in a range then it should not allow the range to be chosen - am i correct?
Kunal
@seanhoots I have another issue that I havenāt seen addressed in this topic. I have a picker in a group that gets reset after save but when I load new data in the group, the previous value is visible in the picker as initial content.
The picker is setup to only show initial content conditionally (when the field is not empty), but for some reason it shows the previous value each time. No matter how I reset the group.
Could there be an issue with resetting the field? When I open the group for the first time in the session, the field is indeed showing empty (when condition is not met), so it does work initially.
Any insights would be very helpful! Otherwise, Iāll have to go back to the default picker for this. Thanks!
Hi @vincent56, the issue with reset has been discussed here on this thread. Yes when you call the bubble reset action it doesnāt reset the custom plugin. I actually reported it to bubble and they asked me to file a bug report but I forgot to do it.
As a work around I created a reset action specifically for the date/time picker so you could reset it when you reset the group. But some users reported the reset was causing some issues for them. See the comments just above your previous comment.
To be honest Iāve not had time to look at this plugin for some time. I guess itās time to take a look at it and fix all reported issues.
Thanks
With regards to this, the 'date selected' event is the same as a 'value changes' event. I could rename it but for backward compatibility i will keep it like that for now. I just tested the picker in a RG and the event works on only the selected picker. Let me know if youāre still facing this issue.
Youāre right and i think this is something @Bubble will have to answer. That is, when a custom plugin element is hidden, its value is null but for the built-in elements their values are available.
Weāll add a way to initialize states, basically a way that will let you write a function to define the initial value of the state, even if the element isnāt visible yet. Weāll do that this week.
Hey guys, is anyone having issues where their Air Date/Time picker isnāt working anymore without upgrading or changing anything? Iāve gotten two people reporting their picker not working.
Please if youāre experiencing let me know and also file a bug report.
Iām getting inconsistent results with my testing. Itās working for some of my own apps and not working for some using the same version.
EDIT:
I think iāve seen what the issue is. It looks like when the picker is in a group, it doesnāt work anymore.
Iāve filed a bug report.
Please @Bubble could you guys quickly take a look at this for me. I have a lot of people using the plugin and iāve started getting complains.
Thanks
We follow up with @seanhoots with a change he should make to his code to work reliably. It should not be too big of a fix on his end.
Fundamentally, when you write a plugin, you should not expect the div to be already in the DOM, so you should access it from instance.canvas, not by using document.getElementById(ID).
Thanks 
