Issues with LD and Maverick's jquery

[rww]

Running LoCo Directory on a server with Maverick causes the date and time pickers on the page for creating a new event to stop working. One problem is that LD uses "/media/jquery-ui/css/css/smoothness/jquery-ui.css", which doesn't exist in Maverick's jquery packages (though "/media/jquery-ui/css/smoothness/jquery-ui.css" does and appears to be the right file). Even when that's fixed, only one of the pickers work. Firefox's error log reports:

Error: $.widget.prototype._trigger is undefined
Source File: http://127.0.0.1:8000/media/jquery-ui-timepicker/js/ui.timepickr.min.js
Line: 51

Everything works fine when running the server on Lucid, so this is likely due to a change between Lucid and Maverick's jquery versions.

[Adnane Belmadiaf (daker)]

try to grab ui-timepickr.js & all the dependencies from the svn
http://code.google.com/p/jquery-utils/source/browse/#svn/trunk/standalone/ui-timepickr/src
then see if it solve the problem.

[Daniel Holbach (dholbach)]

This should be fixed in ./teams/management/commands/init-ld.py

[Adnane Belmadiaf (daker)]

Do we still have problem after the Maverick release ?

[Ronnie (ronnie.vd.c)]

I still got the error: "$.widget.prototype._trigger is undefined" in firebug on maverick

[Ronnie (ronnie.vd.c)]

I got jquery 1.4.2 and jquery-ui 1.8

[Ronnie (ronnie.vd.c)]

There is already a bug for this on the developer page of timepicker:
http://code.google.com/p/jquery-utils/issues/detail?id=53

The following proposed solution (grabbed "jquery.utils.js", "jquery.strings.js" and "ui.timepickr.js" from trunk in SVN.) did not work for me. The bug is from june 2010 and still not fixed, so i guess it wont be fixed in the near future

There are alternative timepickers
http://plugins.jquery.com/project/timepicker-addon
http://plugins.jquery.com/project/jquery-UIstyle-timepicker
http://plugins.jquery.com/project/timepicker

Maybe these will work with the newer version of jquery

[Adnane Belmadiaf (daker)]

Since the actual dev environment is Precise, i'll mark this as fixed.