Hi @carinaa,
I could replicate this issue on my local installation as well.
I’ve added this issue to our bug tracker and it should be fixed in upcoming update cycles.
To temporarily fix this issue, please take a look at this file: ``
- After that find this code:
$('#mec_start_date').datepicker(
{
changeYear: true,
changeMonth: true,
dateFormat: 'yy-mm-dd',
gotoCurrent: true,
yearRange: 'c-3:c+5',
});
$('#mec_end_date').datepicker(
{
changeYear: true,
changeMonth: true,
dateFormat: 'yy-mm-dd',
gotoCurrent: true,
yearRange: 'c-3:c+5',
});
$('#mec_date_repeat_end_at_date').datepicker(
{
changeYear: true,
changeMonth: true,
dateFormat: 'yy-mm-dd',
gotoCurrent: true,
yearRange: 'c-3:c+5',
});
$('.mec_date_picker').datepicker(
{
changeYear: true,
changeMonth: true,
dateFormat: 'yy-mm-dd',
gotoCurrent: true,
yearRange: 'c-3:c+5',
});
if( typeof jQuery.fn.datepicker !== "undefined" ){
$('#mec_start_date').datepicker(
{
changeYear: true,
changeMonth: true,
dateFormat: 'yy-mm-dd',
gotoCurrent: true,
yearRange: 'c-3:c+5',
});
$('#mec_end_date').datepicker(
{
changeYear: true,
changeMonth: true,
dateFormat: 'yy-mm-dd',
gotoCurrent: true,
yearRange: 'c-3:c+5',
});
$('#mec_date_repeat_end_at_date').datepicker(
{
changeYear: true,
changeMonth: true,
dateFormat: 'yy-mm-dd',
gotoCurrent: true,
yearRange: 'c-3:c+5',
});
$('.mec_date_picker').datepicker(
{
changeYear: true,
changeMonth: true,
dateFormat: 'yy-mm-dd',
gotoCurrent: true,
yearRange: 'c-3:c+5',
});
}
Hope it helps 