In libraries.module at line 33, the code assumes that you put it into sites/all/libraries directory, this is not mandatory since anyone can create his own directories structure for different purposes, so the line

    $path .= 'sites/all/libraries/' . $library;

must be changed to

    $path .= drupal_get_path('module', 'libraries') . '/' . $library;
CommentFileSizeAuthor
libraries_get_path.patch871 bytesCristhian
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

tstoeckler’s picture

tstoeckler
he/him
Primary language German
Location Essen, Germany
CreditAttribution: tstoeckler commented
Category: bug » support
Status: Patch (to be ported) » Postponed (maintainer needs more info)

I don't quite understand your reasoning.
The path we are talking about is for a library so it must be in a sites/.../libraries directory, not in a sites/.../modules directory, which is where the libraries module is.
So this is correct:
sites/[all|]/libraries/
and this is wrong:
sites/[all]|]/modules/libraries/
Changing to support request, because I don't think there is anything to be fixed here.

sun’s picture

sun
Primary language German
Location Karlsruhe
CreditAttribution: sun commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)

Yes, this issue is bogus. As the project page explains, Libraries API forms a new, central location to put and have external libraries -- next to modules and themes. Each library must be understood like a single module or a single theme; each one of them is self-contained, is an own project and has an own version.