Hi Daryl,
Does this happen with every instance of date picker, or just on this one page? How was this one installed, (i.e. through CSS Formbuilder)? What happens if you create just a datepicker field on a fresh page using CSSFormBuilder, do you get the same error?
I can't seem to get mine to fault in the way yours does. I created a single field and changed the date range, and tested choosing one mm/dd/yyyy, and then changed it to a year later and subsequently several later dates.
Do you have just the one datepicker in your form, or two (perhaps a start date and an end date) because there was some custom code linked to in which the options of one date depended on the value of the other that had some glitches in practice.
I'm assuming you have added a line to the page script to give a custom date range. Perhaps you could change the range and see if that makes any difference?
The datepicker javascript page code produced for me by CSSFB is:
<script type="text/javascript">
$(function(){
$('#fieldset_group_date').datepicker({
changeMonth: true,
changeYear: true,
yearRange: '1950:2025',
onClose: closeDatePicker_fieldset_group_date
});
});
function closeDatePicker_fieldset_group_date() {
var tElm = $('#fieldset_group_date');
if (typeof fieldset_group_date_Spry != null && typeof fieldset_group_date_Spry != "undefined") {
fieldset_group_date_Spry.validate();
}
var docElm = document.getElementById("fieldset_group_date");
var tBlur = docElm.getAttribute("onBlur");
if (!tBlur) tBlur = docElm.getAttribute("onblur");
if (!tBlur) tBlur = docElm.getAttribute("ONBLUR");
if (tBlur) {
tBlur = tBlur.replace(/\bthis\b/g, "docElm");
eval(tBlur);
}
}
</script>
apart from the line specifying a date range (in blue).
Do you have a page you could link to where we can see this behaviour?
If you get completely stuck, you could try one of the examples here.