Is this still an issue in the latest release version?
If yes, please attach the sample survey. Thank you.

Yes. Here is the sample survey: http://uksurveys.hkipop.com/index.php/114454?newtest=Y&lang=en

I have exported the survey as an .lsa file, attached. Is that what you need?

We've switched to limesurvey3.3.0+180209 and the bug still appears.

This bug report is for DateTime pickers, but we're seeing a related issue with Date pickers. Sometimes (but not always) the console will say "uncaught exception: bootstrap-datetimepicker requires Moment.js to be loaded first" and the Date picker will fail to open when clicked. Perhaps there's a race condition happening?

I tried to reproduce this on Linux without success. The date picker works fine. The picker works fine in your link, too. Can this issue be closed?

Markus could you have a look to the moment.js loading problem?

To use the datetimepicker moment has to be loaded as a package in the theme.

Reporter say: " Sometimes (but not always) the console will say "uncaught exception: bootstrap-datetimepicker requires Moment.js to be loaded first" and the Date picker will fail to open when clicked. "

could you check how the date picker's js and moment js are loaded?

After upgrading to LimeSurvey 3.4.3+180227, the moment.js loading problem no longer appears. On all themes, DatePickers and DateTimePickers will no longer fail to open. Thank you for the fix. :-)

We still have the issue that when placing two identical DateTimePickers in a survey, the first one will consistently produce a DatePicker instead. See attached screenshots, created from the same sample survey I linked above: http://uksurveys.hkipop.com/index.php/114454?newtest=Y&lang=en

DateTime-2.png (57,894 bytes)   

DateTime-2.png (57,894 bytes)   

DateTime-1.png (59,837 bytes)   

DateTime-1.png (59,837 bytes)   

ok thank you for that feedback!
could you please open a new bug report for the double date time picker problem?

I have just noticed that DateTimePicker 1 has a small clock icon at the bottom that, when clicked, reveals the "time" side of the DateTimePicker. This is not clear enough, and it is not consistent. Please label the icon and/or cause the two identical DateTimePickers to function the same way.

@LouisGac New bug report, as requested: https://bugs.limesurvey.org/view.php?id=13450

You can close this issue now.

Ee still face this problem but only in Mozilla Firefox 63 (64-bit) and Firefox 60.3.0 esr (32-bit), IE is ok
We have currently version 3.14.11 running on our server.

here is the error from console window in Firefox
uncaught exception: bootstrap-datetimepicker requires Moment.js to be loaded first
TypeError: $.fn.datetimepicker is undefined[Weitere Informationen]

After reloading the page, I can click on the Icon and the Datepicker appears.

@halliballi123 : since it close since 3.4.x : i think you can report a new issue.

Surely related to ajax-mode …

Are you using a self built theme?
Please add moment in the packages of your theme then.

You are right, I have a self built theme. That might cause the problem. but and where do I get this Moment.js?
Thank you

moment is part of the general packages.
You can check the theme options and go to the advanced tab.
in the very last row with the label "Packages to load" should have this content:

{"add":["pjax","font-noto","moment"]}

you may leave out font-noto if you don't need it.

moment is needed for expression ? No ?
If yes : must put in https://github.com/LimeSurvey/LimeSurvey/blob/3a7bbff279f2ae3fbf5278c73a4dbd6e427f00d4/application/config/packages.php#L33 (develop)

And if not : must create question_date package with this depend.

Ok, I found moment-with-locales.min.js and I added the file in config.xml.
But the error still shows up.

Do I have to add the file somehow different? for Ajax?

sorry, forget my last message (I sent it and your answers where already there)

Thank you Markus. That was the solution for my problem!!!

can I put that somehow into the config.xml?
Otherwise I have to add that configuration everytime I re-install that theme.

found it:

inside <engine> tag
add:
<packages>
<add>pjax</add>
<add>moment</add>
<add>font-noto</add>
</packages>

Ok Great.
I like it when a bug solves itself. :D