Closed (fixed)
Project:
Bootstrap
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
31 Dec 2012 at 21:58 UTC
Updated:
21 May 2013 at 14:50 UTC
Jump to comment: Most recent file
Comments
Comment #1
andregriffin commentedYes, this needs to be done for js. It was sort of taken care of for the CSS with this issue: #1858418: Make set location of the bootstrap library more easily modified.
Comment #2
frankbaele commentedadded a patch to fix this problem and while is was in that code, also removed the jquery cdn in favor of using the jquery update module.
The reason why i propose to remove my own jquery cdn code, its not a bad solution but i think we should choose one way too update the jquery version. And the most commonly used way is the jquery update module.
http://drupal.org/node/1846736
Comment #4
frankbaele commented#2: remove_jquery_cdn_and_use_info_file.patch queued for re-testing.
Comment #6
wundo commentedHi Frank,
Could you break the patch in two?
There is a separated issue for the jquery-cdn thing.
Cheers,
Fabiano
Comment #7
frankbaele commentedno problem
Comment #8
k4v commentedI think the cleanest way to handle the JS is to put it in a helper module with library support. That way we can also make use of the modular Javascript in Bootstrap, and only include parts needed in a project.
Check out http://drupal.org/project/bootstrap_api.
I'm working with blackice2999 on this. We would appreciate it, if we could join our efforts here.
Comment #9
markhalliwellThis isn't a problem with the new sub-theme methods now committed to dev via #1844448: Add sub-theme starter kit. A sub-theme must either use the Boostrap CDN or supply it's own CSS and JS. The base theme no longer attempts to load the Bootstrap JS unless specified as using the CDN.