Closed (fixed)
Project:
Modernizr
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Jan 2013 at 20:32 UTC
Updated:
29 Jan 2013 at 06:20 UTC
Jump to comment: Most recent file
Comments
Comment #1
ruplYou're correct. This stems from the fact that the module opts to use Libraries API but can still operate if you do not have it enabled. You're right though, the instructions should be more specific and more in line with the Status Report page which correctly handles all situations.
This will be resolved before the final 3.0 release.
Next major release after 3.0 will require Libraries API. It's the best way to handle 3rd party libs, and it will reduce this module's codebase/documentation significantly.
Comment #2
marcvangendOK, thanks for your response. Libraries API is a good choice afaic, it's used a lot and it would sure help to get rid of this confusing situation.
Until it's resolved, I hope that people who are as confused as I was, will find this issue and know what to do. Just install Libraries people!
Comment #3
ruplI committed this patch to dev. It re-words the instructions based on the current status of Libraries API. If Libraries is enabled then the instructions mention
sites/all/libraries/modernizr, otherwise a location inside the path of the Modernizr module is used.