October: Uncaught TypeError: Cannot read property '0' of undefined

[leocavalcante]

Expected behavior

Date picker widget to show up next to the input.

Actual behavior

It doesn't appear and the following errors shows up at the console on every click:

storm-min.js?v349:2380 Uncaught TypeError: Cannot read property '0' of undefined

Time picker seams all right, its only for the dates.

Reproduce steps

Just add a datepicker field with any mode.

October build

349

[daftspunk]

Unable to reproduce. This might be a single user issue. Do you have another October installation you can test with?

[xhepa112]

This is happening to me too.
I have used Builder to develop a plugin maybe is Builder related error.

[leocavalcante]

I'm not using Builder on this project, it is using Translate, Editable and User.
Haven't time yet, but I'll hack a little more into this to get more info.

[xhepa112]

I cleared the cache and logout from the system.
I 'm not sure if this did the trick but it is working now.

[leocavalcante]

Hm! I did a clean install, added the same plugins and it's working. Probably something with my project. I will reopen if I find anything else.

[leocavalcante]

Weird, something about the Locale. I switched back to en then set again to pt-BR and its working now :confused:

[daftspunk]

Code shows it is looking for a locale that doesn't exist in pikaday

opts.i18n.months[i]+'</option>');}

We will update it today and hopefully that improves the locale support.

Refs #2237

[daftspunk]

I noticed da was missing locale information. It was compiled in 5af9fcbfdcc1c163f0113a1df7adbe03b3cd3bdf

This might have been the cause.

[ekstremedia]

I have the same issue on build 419. Was also missing a language file, made the missing file, but still get one error: storm-min.js?v419:2395 Uncaught TypeError: Cannot read property '0' of undefined.

Edit: Apparently my language was set to Bali in the backend, hehe, dont know how that happened! Set it back to Norwegian, now it works again.

[r-guimaraes]

I know that you guys have already found the solution, but just complementing ...

I set the locale to "Brazil", and timezone to "America/Sao_Paulo" (because obviously that was just my case) at "Profile > Back-end preferences", and that did the trick

Thanks for the answers above

[CasonWebDev]

Is too late to anwser that, but, i got the error only now, and i solved changing pt-BR to pt-br, is stupid i know, but, i think this is the cause ahahaha

[bennothommo]

@CasonWebDev Never too late to add any answers. If anyone has the same issue, hopefully they'll come across this issue and your answer ;)