Replacing the shipped jQuery library

Hi all,

I'm having problems that appear to be caused by a bug in jQuery 1.1.1 and was wondering if it is safe to replace that with the latest version (1.2.1)?

Cheers,

Thomas

By default, i'd answer "yes" because whatever the software, new versions
often (not to say everytime) improve existing features and fix some
stargate sized security holes.

I'd make an exception if 1.2.1 is a .dev version for exemple, in this case
i'd keep the 1.1.1, waiting for a next stable release.

Good luck.

Etienne.

On Fri, November 9, 2007 4:48 am, Thomas Sutton wrote:

Hi all,

I'm having problems that appear to be caused by a bug in jQuery 1.1.1
and was wondering if it is safe to replace that with the latest
version (1.2.1)?

Cheers,

Thomas
_______________________________________________
spip-en@rezo.net - http://listes.rezo.net/mailman/listinfo/spip-en

Hello Thomas,

JQuery is stored in two places in the template directory, so the default version is in:
dist/javascript/jquery.js
dist/jquery.js.html
(I am not really sure why there are two files... one is probably accessed as a template, from the public site, the other one with a simple find_in_path)

Anyway, as this is in the template directory, you can place a new version without modifying SPIP distribution by putting your version of jQuery in your own template directory (probably "squelettes").
So, if something goes wrong, you can easily go back...

I checked the SVN version of SPIP 1.9.3, and they are already using jQuery 1.2.1 for this one:
http://trac.spip.org/trac/spip/browser/spip/dist/jquery.js.html

Pierre

Thomas Sutton wrote:

Hi all,

I'm having problems that appear to be caused by a bug in jQuery 1.1.1 and was wondering if it is safe to replace that with the latest version (1.2.1)?

Cheers,

Thomas