Closed (fixed)
Project:
Modernizr
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
14 Sep 2011 at 10:56 UTC
Updated:
27 Oct 2011 at 16:51 UTC
Jump to comment: Most recent file
Comments
Comment #1
iler commentedI created a patch for this one. Also added check to see if the modernizr.min.js really is in sites/all/libraries/modernizr/ directory. If the file isn't there user will get a warning message displayed in the admin area of Modernizr module.
Comment #2
tamasd commentedThe libraries support was there, the problem was that I forgot to modify the code in hook_init().
This is fixed in commit: f8cbc8343d716af9ac2e65a50749f4bc7b37f48f.
Comment #3
ruplComment #5
klonos...why was this opened if we have #999870: Use the Libraries module? Or perhaps there was need to solve this in a per-branch basis by opening two separate issues (one for 7.x + one for 6.x)?
Comment #6
klonosThe new 7.x dev seems to work just fine, but there is one minor WTF...The site status displays "Modernizr is installed and ready to use" (it also detects 2.0.6 as version) even though I remove the modernizr.js file from the../sites/all/libraries/directory or the whole directory altogether?!?...don't mind me. There was some caching mechanism implemented since the last dev I was using. Crealing caches made the status "complain" as expected ;)
Comment #7
klonosComment #8
klonos...sorry for the noise.