gatopinches

From what I’ve seen, there are plenty of problems with the datepicker provided by this plugin.
Don’t get me wrong: it is an awesome plugin and free, so, no complaints here, but given that most if not all people use customized templates, you should consider including an option to modify this particular behavior.

I was able to somewhat display it properly with some custom css, this not being an ideal situation. I wouldn’t call it a bug, but it is a very restrictive condition that could sway people from using your excellent plugin.

I had the same problem and was able to work around it with this custom css placed in the page that holds the form:

input, textarea, select, .seldiv, .select2-choice, .select2-selection–single {
display: block !important;
font-size: 14px !important;
line-height: initial !important;
margin: 9px 0px 0px 0px !important;
padding: 10px 15px 10px 15px !important;
border-style: solid !important;
border-radius: 2px !important;
font-weight: normal !important;
border: 1px solid transparent !important;
margin-top: -3.8em !important;
max-width: 92%;
min-width: 92%;
}

.um .picker__month {
margin-top: 1em;
}

it’s not been sanitized so, maybe, some of the operators might not be needed and there’s no way to tell if they’ll work for your template, but it wouldn’t hurt to give it a try since the arrangement of elements in your screenshot is pretty similar to what I was having.

Hope it helps!

Make sure that the “logout” buttons are pointing to the logout page, which is essentially a blank page.
I had some weird behavior with it too but got resolved by just pointing it to an empty page.

I re-selected all pages for each event, the same ones, and for some reason the page started working again. Seems it was un po pazzo, solamente ??

come sempre, grazie mille per l’aiuto!

First of all, thanks a lot for your quick response.

Yes, I did set up everything correctly. Actually, it was running perfectly up until a couple of weeks ago.

I’ve not yet updated the plugin to the latest version, aiming to solve this problem first; it’s still running 2.1.1. Do you think I should update first and see how that goes?.

Excellent!.
Thanks a million for your swift response and plug-in update!.