Search

Hey everybody,

I just finished working on my first (very tiny) extension: a jQuery supplier. Seeing at least three extensions using jQuery and all of them supplying it by themselves, I thought one single extension providing jQuery for all the others could become handy some day.

Tell me what you think.

I’m confused how this works.

I have enabled it, but now what?

@NickToye: For now its not really useful but it may happen that extensions without their own copy of jQuery will be released. In this case, you will need this extension.

Hi phoque — grats on the first extension :-)

Unfortunately I think it may have been time wasted :-/ There was some lengthy discussion regarding the use of JavaScript libraries:

http://getsymphony.com/forum/discussions/631/

Which resulted in the beginnings of an extension designed to manage the inclusion and dependencies thereof:

http://getsymphony.com/forum/discussions/760/

However these are pretty much negated now that jQuery is included in the core by default. Scott has rewritten the admin.js to use jQuer and the library is now included in the backend for other extensions to use. This is available on the latest version of Symphony on Github, which will eventually become 2.0.3. When this happens, extensions reliant on jQuery can be rewritten to remove jQuery from their own assets, in favour of using the single Symphony version.

Ah, bugger… I was already wondering why nobody else came up with that idea.

But don’t worry, I already have a second extension (wich is using jQuery) up my sleeve :-)

Create an account or sign in to comment.

Symphony • Open Source XSLT CMS

Server Requirements

  • PHP 5.3-5.6 or 7.0-7.3
  • PHP's LibXML module, with the XSLT extension enabled (--with-xsl)
  • MySQL 5.5 or above
  • An Apache or Litespeed webserver
  • Apache's mod_rewrite module or equivalent

Compatible Hosts

Sign in

Login details