BFA 2 beta ready for testing!

I just pushed v2.0.0-beta3 which fixes a few issues and errors.

Please download the latest beta for testing:
https://downloads.www.ads-software.com/plugin/better-font-awesome.2.0.0-beta3.zip

. . . and as always, thanks for your support!

I have not tested this yet however, using the Cdn code for 5.1 and having it in my site for at least a week, I believe that NEWER is not always better. Why? The 5.1 version in my secondary navigation gives RENDER BLOCKING JAVA SCRIPT and above fold CSS that google page speed displays in your face quite bluntly!

I have the 4.7 widget in my footer and it is giving me a 100% score (as in my older site)…. when I remove 5.1 from my secondary navigation CSS. on top.

I have not tried 5.2 yet to see if the same render blocking css above the fold is present.
Can the 4.7 still be used safely in the near future?
Howard

I’m getting the following error with the beta:

Warning: array_map(): Argument #2 should be an array in /shared/httpd/originsc/www/wp-content/plugins/better-font-awesome/vendor/mickey-kay/better-font-awesome-library/better-font-awesome-library.php on line 880

Modifying the get_icon_array_version_5() function to this seems to fix it:

https://gist.github.com/tracyfloyd/72b2d991651aeb082783b32ae3dde342

@tracyfloyd – You, sir, are an absolute genius. Thank you for sharing!

I have just discovered this plugin but from the description of it it looks beautiful! Thanks a lot for the time & effort that surely must’ve gone into this! I will be installing & testing the beta plugin soon!

Well, it was a short-lived test ?? The plugin installs & activates fine, but clicking the “insert icon” button does nothing & gives this error in the console

Uncaught TypeError: Cannot read property 'length' of null
    at c._createIconpicker (fontawesome-iconpicker.min.js:20)
    at new c (fontawesome-iconpicker.min.js:20)
    at HTMLSpanElement.<anonymous> (fontawesome-iconpicker.min.js:20)
    at Function.each (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-position,underscore,moxiejs,plupload&ver=4.9.8:2)
    at a.fn.init.each (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-position,underscore,moxiejs,plupload&ver=4.9.8:2)
    at a.fn.init.a.fn.iconpicker (fontawesome-iconpicker.min.js:20)
    at HTMLSpanElement.<anonymous> (admin.js:32)
    at HTMLBodyElement.dispatch (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-position,underscore,moxiejs,plupload&ver=4.9.8:3)
    at HTMLBodyElement.r.handle (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-position,underscore,moxiejs,plupload&ver=4.9.8:3)

this is on latest wordpress with no other plugins & 2017 theme. The current non-beta version of the plugin does work fine though

• This reply was modified 6 years, 2 months ago by maustin89.

Is there any chance of supporting the Pro CDN and icons?

Hi all,

Sorry for all the issues. I actually recently spoke to the official Font Awesome team about some of these issues, and even the possibility of them taking on this project. Here are the outcomes:

1. Though they were interested, they have decided not to take on this plugin
2. They acknowledged that there API/interface changed (which is the cause of this issue), and unfortunately said they don’t intend to provide a guaranteed publicly accessible API with a clear SLA (I understand their decision, though I can’t say I’m pleased)
3. They weren’t yet sure if they would provide support for publicly accessing pro data based on a customer key (I started to work on this feature already, however it’s not achievable without the FA folks making this publicly accessible)

In terms of next steps, I intend to resolve the issue of the errors above as best I can. It’s tough not having any guarantee that the FA data model won’t suddenly change under the hood, however I will do my best to build in safe guards and will release another beta for testing. I’ll do my best to make this happen ASAP. I hate keeping y’all waiting, AND life is full of many things these days ??

Thanks for your patience, your loyalty to BFA, and for all the great feedback!

– Mickey

Hi,

Just to report another error that I’m seeing on some of my sites (on version 2.0.0-beta3).
Undefined variable: search_terms
at line 886 in
wp-content/plugins/better-font-awesome/vendor/mickey-kay/better-font-awesome-library/better-font-awesome-library.php:886

Thanks for a great plugin, and sorry you’re having frustrations with the FA interface.

– Chris

Any updates?

Hi Mickey,

thanks for the hard work you put into this plugin.

Just wanted to report we have this error in WP control panel.

Better Font Awesome: Version 2.0.0-beta3

——————————————————————-
Better Font Awesome

API Error
The attempt to reach the jsDelivr API server failed with the following error: 404: Not Found (URL: https://cdn.jsdelivr.net/gh/FortAwesome/[email protected]/advanced-options/metadata/icons.yml)

Don’t worry! Better Font Awesome will still render using the included fallback version: 4.7.0

Solution
This may be the result of a temporary server or connectivity issue which will resolve shortly. However if the problem persists please file a support ticket on the plugin forum, citing the errors listed above.
——————————————————————-

Thanks

Ok looks like its been moved to

https://github.com/FortAwesome/Font-Awesome/blob/master/metadata/icons.yml

Will do a regex through your source code and replace the old string with the new string and report back

** EDIT **
Looked at the source, unsure what to do so didnt proceed changing anything

• This reply was modified 5 years, 11 months ago by mongobongo.

The same problem here! Please help.

Thanks,
Robert

As @mongobongo pointed out, it looks like the cdn.jsdelivr.net site no longer delivers the FA assets, so the references to it need to be updated. I was able to get it working again with the following changes to
wp-content/plugins/better-font-awesome/vendor/mickey-kay/better-font-awesome-library/better-font-awesome-library.php

Around line 551:
Replace:
$url = self::JSDELIVR_ICON_METADATA_BASE_URL . $version . self::JSDELIVR_ICON_METADATA_FILE_PATH;

With the raw file on github. I’d feel better about this if it was hosted on the FontAwesome CDN, but I can’t find any other official link to it:
$url = 'https://raw.githubusercontent.com/FortAwesome/Font-Awesome/master/metadata/icons.yml';

Additionally, the url to the css also needs to be updated.

Around line 694:
Replace:
$this->stylesheet_url = '//cdn.jsdelivr.net/gh/FortAwesome/Font-Awesome@' . $version . '/web-fonts-with-css/css/fontawesome-all' . $this->get_min_suffix() . '.css';

With the FontAwesome CDN url:
$this->stylesheet_url = 'https://use.fontawesome.com/releases/v' . $version . '/css/all.css';

• This reply was modified 5 years, 11 months ago by tracyfloyd.

There is no issue with jsDelivr, it’s just that Font Awesome moved some files in the latest release (and jsDelivr mirrors those changes). The new URL is https://cdn.jsdelivr.net/gh/FortAwesome/[email protected]/metadata/icons.yml. For the previous FA versions, the old URL still works of course.