Library is missing even though it is installed

Created on 2 September 2022, about 2 years ago
Updated 7 August 2024, 4 months ago

Problem/Motivation

I've installed the module and the library can be found at:
/home/userid/public_html/web/libraries/fontawesome-iconpicker

The status report keeps saying: "The fontIconPicker library could not be found. To use the Font Awesome Iconpicker, please verify that the fontIconPicker library is installed correctly. Please see the Font Awesome Iconpicker submodule README file for more details."

I read the file and tried changing the address to match what is in there: /home/userid/public_html/web/libraries/fonticonpicker--fonticonpicker/

Still does not work.

πŸ’¬ Support request
Status

Fixed

Version

3.0

Component

User interface

Created by

πŸ‡ΊπŸ‡ΈUnited States jsimonis

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States BEGRAFX Laconia, New Hampshire

    I'm getting the same message. I've installed the library, but still get the message.

    Something I notice, the profile page says in part:

    Please download the library from the above location and put it in libraries folder. After that unzip and rename the folder to 'fontawesome-iconpicker' (i.e. remove the version suffix). After you do it, the fontawesome-iconpicker.js file should be available at /sites/all/libraries/fontawesome-iconpicker/dist/js/fontawesome-iconpicker.js.

    I'm presuming that this is a D7 reference (and should probably be updated, or appropriately notated); and that root/libraries/fontawesome-iconpicker/dist/js/fontawesome-iconpicker.js is the correct path for a Drupal 10 install.

  • πŸ‡ΊπŸ‡ΈUnited States jsimonis

    Has anyone gotten this working? I tried the composer code listed above, but got:

    Could not find a matching version of package npm-asset/fonticonpicker--fonticonpicker. Check the package spelling, your version constraint and that the package is available in a stability which matches your minimum-stability (stable).

  • πŸ‡©πŸ‡ͺGermany D34dMan Hamburg

    Could not find a matching version of package npm-asset/fonticonpicker--fonticonpicker. Check the package spelling, your version constraint and that the package is available in a stability which matches your minimum-stability (stable).

    could you please try to change "minimum-stability": "stable", to "minimum-stability": "dev", in your composer.json and try again?

    To know more about minimum-stability and its implication, please check out documentation on https://getcomposer.org/doc/04-schema.md#minimum-stability

  • πŸ‡ΊπŸ‡ΈUnited States jsimonis

    Got this:

    Could not find a matching version of package npm-asset/fonticonpicker--fonticonpicker. Check the package spelling, your version constraint and that the package is available in a stability which matches your minimum-stability (dev).

  • #4 worked for me.

    For people getting npm errors like "Could not find a matching version of package npm-asset/fonticonpicker--fonticonpicker", you might need to tell your composer file where to look for npm packages, and where to install them.

    If so, first you need the oomphinc/composer-installers-extender plugin for composer, this allows any package to be installed to a directory other than the default vendor.

    composer require -W --ignore-platform-reqs oomphinc/composer-installers-extender

    Now we have to make some changes to composer.json to tell it where to look for these packages and what to do with them.

    Under the 'repositories' section near the top, we add packagist.org as a code repo

    {
        "type": "composer",
        "url": "https://asset-packagist.org"
    },

    In your "extra' section of composer, you need to allow npm packages:

    "extra": {.....other configs
     
        "installer-types": [
            "npm-asset"
        ]
    }

    Also in the 'extra' section, you need to tell composer where to install the npm packages, in this case in the libraries folder, by adding npm-asset as a type and vendor to the "web/libraries/{$name}" block

    "web/libraries/{$name}": [
          "type:drupal-library",
          "type:npm-asset",
          "vendor:npm-asset"
    ],

    Finally running
    composer require npm-asset/fonticonpicker--fonticonpicker
    should add the library to your composer files. On my site this created a 'fonticonpicker--fonticonpicker' folder in the libraries directory, and the site error about missing library went away

  • #4 worked for me.

    For people getting npm errors like "Could not find a matching version of package npm-asset/fonticonpicker--fonticonpicker", you might need to tell your composer file where to look for npm packages, and where to install them.

    If so, first you need the oomphinc/composer-installers-extender plugin for composer, this allows any package to be installed to a directory other than the default vendor.

    composer require -W --ignore-platform-reqs oomphinc/composer-installers-extender

    Now we have to make some changes to composer.json to tell it where to look for these packages and what to do with them.

    Under the 'repositories' section near the top, we add packagist.org as a code repo

    {
        "type": "composer",
        "url": "https://asset-packagist.org"
    },

    In your "extra' section of composer, you need to allow npm packages:

    "extra": {.....other configs
     
        "installer-types": [
            "npm-asset"
        ]
    }

    Also in the 'extra' section, you need to tell composer where to install the npm packages, in this case in the libraries folder, by adding npm-asset as a type and vendor to the "web/libraries/{$name}" block

    "web/libraries/{$name}": [
          "type:drupal-library",
          "type:npm-asset",
          "vendor:npm-asset"
    ],

    Finally running
    composer require npm-asset/fonticonpicker--fonticonpicker
    should add the library to your composer files. On my site this created a 'fonticonpicker--fonticonpicker' folder in the libraries directory, and the site error about missing library went away

  • πŸ‡°πŸ‡ͺKenya gwanjama Nairobi

    #10 worked for me...thanks daveban β†’

  • πŸ‡©πŸ‡ͺGermany D34dMan Hamburg
  • Status changed to Needs review 4 months ago
  • πŸ‡©πŸ‡ͺGermany D34dMan Hamburg

    This should be fixed.
    Instead of relying on composer to manage 3rd party library beyond our control, added dependency to https://packagist.org/packages/d34dman/vanilla-icon-picker to resolve the issue without much composer hackery. Please test and let me know if this works for you.

    Try,
    composer require drupal/fontawesome_iconpicker:^3

  • πŸ‡©πŸ‡ͺGermany D34dMan Hamburg

    Fixed in version 3.0.0-alpha5

  • Status changed to Fixed 4 months ago
  • πŸ‡©πŸ‡ͺGermany D34dMan Hamburg

    After a much await, we have a working composer installation (fix in 3.x-dev, 3.0.0-rc1)

    Marking this as fixed.

    Check https://www.drupal.org/project/fontawesome_iconpicker/issues/3359673#com... πŸ› Cannot install on Drupal 10 with composer Fixed for report.

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

Production build 0.71.5 2024