Peter Haworth

OK, thanks but how can I change the query name then? There's no Save button

This is still an issue for me and in fact means I will not be able to use datepicker unless it's resolved. It's become worse than the original report as...

I would like this enhancement too. Maybe the global setting could be handled in the locale file for whatever language is chosen with a per field override?

Is this plugin still supported?

And I do. On Wed, Sep 6, 2017 at 10:43 AM, Antti Haapala wrote: > well the docs very clearly say that if e.isDefaultPrevented() returns > *false*, then validation failed....

Is there a fix for this yet? If not, how do I get v1.7.0 since apparently that works. Never mind, my fault, permissions were wrong on the datepicker.js file.

This problem is worse now. The User Agent for Chrome running on my Pixel tablet is Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/[127.0.0.0](http://127.0.0.0/) Safari/537.36 It no longer contains...

Tried that and still get the same problem. I very much doubt this is a Mustache problem because all my other templates are working correctly, just wish I could figure...

OK, I figured this out - the file permissions were set incorrectly, allowing read access to User only. Once I fixed that, all works OK. Not sure if it's possible...

Yes, they were set to #600 when I was getting the error and I changed them to #644 to fix the problem. I don't know enough about website file permissions...