FFont Awesome plugin is broken

OK, here’s a pre-release zip file, from our GitHub repo.

But you’re installing via composer, then you should change your composer dependency to target the development branch, like this:

  "require": {
    "fortawesome/wordpress-fontawesome": "dev-fix-js-paths"
  }

After digging into the details, I can see that it’s possible that the root cause of the error message as reported by @lavignechris is different from the one reported by @nipatel. I’d like to see how it works for both of you.

Thanks for the feedback, @ssteckley. Could you say whether you’re installing the plugin using Composer, or installing via the zip file?

Can you say whether your situation involves loading the Font Awesome plugin’s assets from a non-typical location, such as within the Composer vendor bundle of some other theme or plugin?

If you don’t know but would like to find out and let me know, read on. Otherwise, never mind the following:

On a typical installation, like installing from the WordPress plugin directory, or by uploading the plugin’s zip file–and when there’s no other custom WordPress configuration that moves paths around–I’d expect the plugin’s main JavaScript to load from here:

/wp-content/plugins/font-awesome/admin/build/index.js?ver=4.0.2-rc1

(You could inspect this by opening the JavaScript console in the Chrome browser, select the Network tab, typing in a search filter for index.js, and then loading the plugin’s admin settings page. Here’s a screenshot that shows this.)

Or if the plugin is loading through some other plugin’s or theme’s Composer bundle, it might look like this instead:

/wp-content/plugins/plugin-sigma/vendor/fortawesome/wordpress-fontawesome/admin/build/index.js?ver=4.0.2-rc1

Here’s a screenshot of that second scenario.

(NOTE: the name of the JavaScript file would have been different in plugin version 4.0.1. If you, or others finding this, are curious to compare, here’s a screenshot showing what you’d be looking for in 4.0.1.)