Hi this is just a suggestion, but how about integrating this module with Libraries API for the js?

I don't knwo if you knwo it, but it is a cool module that tries to avoid the presence of multiple copies of the same external js/css/.. library.

The integration is fairly simple and if you are interested I can work on it and provide a patch.

Greetings,
Esolitos

Comments

mrpauldriver’s picture

This is a good suggestion which would be more in keeping with normal Drupal practice. Apart from anything, library integration is more robust in terms of module updates.

hatuhay’s picture

Assigned: Unassigned » hatuhay
Status: Active » Needs work

No doubts on it, first priority on next issue.

portulaca’s picture

+1 for the Libraries implementation.

spidersilk’s picture

Yes, I was really startled to see that the directions say to put the downloaded scripts in the module folder - where they'll be overwritten any time the module is updated! I can't recall any module that's required that since Drupal 6 - external script/libraries/etc. normally always go in the libraries folder, where they're safe from being overwritten.

Also - should I be worried that a comment saying it will be "first priority" is three years old and this issue isn't closed yet? :( Is this module still being maintained - the Drupal 7 version, that is? It looks like there have been recent releases of the Drupal 8 version, but nothing for D7 in three years...

asb’s picture

Asking the same question… another year later…

astonvictor’s picture

Status: Needs work » Closed (outdated)

D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.