IPGV&M 7.x-1.23+14-dev
Font-Awesome 7.x-1.x-dev
Font-Awesome Library 4.0.3 located sites/all/libraries/font-awesome

Drupal Status report:

IP Geolocation Views & Maps Font Awesome extension Installed
Font Awesome The Font Awesome library could not be found

Change the library path to sites/all/libraries/fontawesome
Drupal Status report:

IP Geolocation Views & Maps Font Awesome extension The optional Font Awesome directory was not found, so you will not be able to superimpose any Font Awesome symbols on top of your markers
Font Awesome 4.0.3

What is the correct path for font-awesome libraries (meaning, not sure if this is a ipgv&m bug or a font-awesome module bug, or if I am simply doing it wrong)

Comments

RdeBoer’s picture

Assigned: Unassigned » RdeBoer
Status: Active » Fixed

You do not need the font-awesome module. I didn't even know it existed.

The following path needs to exist on your site
sites/all/libraries/font-awesome/css/font-awesome.css

See the README that comes with IPGV&M:

"To install Font Awesome visit http://fortawesome.github.io/Font-Awesome and press the "Download" button.
Unzip the downloaded file into the Drupal libraries directory, typically sites/all/libraries, so that the path to the
essential style sheet becomes sites/all/libraries/font-awesome/css/font-awesome.css"

So you may need to rename the top of your downloaded directory from font-awesome-4.0.3 to font-awesome

mainbrace’s picture

Thank you. Fixed.

Now, I realize that IPGV&M specifies the path in the readme, but when another module expects it somewhere else (or spelled differently), who's to say which is correct? Both? Is it up to the module author to define the associated library installation path?

I realize that this isn't technically a "bug" and is more of a software philosophy question, but do you know if there is a Drupal official standard somewhere that defines an externally-developled library's directory name when used with Drupal (e.g. dash, no dash)?

RdeBoer’s picture

Hi mainbrace,

Re #2. You have a valid point. I don't know about an official standard for naming library folders. And I'm not even sure where to raise this as an issue.

The whole idea about the libraries module is that we have one copy of each library in a central place, but the Libraries module does not enforce a naming convention, nor does it offer great support in dealing with auto-extracting the right library name when that name has a version number embedded.

From a site-builder perspective it would be great if you could just download and drop a third-party library into sites/all/libraries and be done with it -- without having to tweak the folder name.

However, the Libraries module, as far as I know, does not offer the facility to auto-detect the version in a directory name like font-awesome-4.0.3 or to distinguish that from font-awesome-4.0.2.
So as Drupal developers we see ourselves forced to use generic folder names, with the version number extracted by the Libraries module from a file somewhere inside that folder as nominated by the Drupal developer.

As far as folder names go, I myself prefer dropping the version suffix (with the folder name thus becoming font-awesome) over dropping the version suffix AND removing any hyphens (fontawesome), but the maintainer of the https://drupal.org/project/fontawesome module must have felt differently.

And so for now, you (and everybody else) will need to duplicate the library under two names, if both modules are used simultaneously.

I'm happy to come to an agreement on names. I have created this issue: #2168983: Library folder naming convention.

Rik

mainbrace’s picture

great discussion. Im looking forward to see what comes out of the numbered issue you submitted. (ran into this again today with another directory name with a 'dot')

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

Patryk Padus’s picture

In main site there aren't any info about
"From a site-builder perspective it would be great if you could just download and drop a third-party library into sites/all/libraries and be done with it -- without having to TWEAK the folder name."
So pleas add it.

Patryk Padus’s picture

Status: Closed (fixed) » Needs work

Add info to change path to library when in use with Library API to 'font-awesome' (must be without version)

RdeBoer’s picture

See the README included with module and also accessible from project page (http://cgit.drupalcode.org/ip_geoloc/plain/README.txt?id=refs/heads/7.x-1.x):

To install Font Awesome visit http://fortawesome.github.io/Font-Awesome and
press the "Download" button. Unzip the downloaded file into the Drupal
libraries directory, typically sites/all/libraries. If you wish, remove the
version number from the directory name, so that the path to the essential style
sheet becomes sites/all/libraries/font-awesome/css/font-awesome.min.css.
Then enter that path at admin/config/system/ip_geoloc.
You can assemble your own icon set from Font Awesome and other repositories at
fontello.com and download it to sites/all/libraries. Then again enter the path
to the main .css file at admin/config/system/ip_geoloc.

Similarly flaticon icon packs can be selected from http://www.flaticon.com.
First create the directory sites/all/libraries/flaticon, then download and unzip
the pack into that directory, so that the path to the essential style sheet is
sites/all/libraries/flaticon/PACK/flaticon.css, where PACK may be something like
"food-icons".
Then enter that path at admin/config/system/ip_geoloc.
RdeBoer’s picture

Status: Needs work » Closed (outdated)