Call to a member function get_error_code

+1

I am getting the same result when activating on Multisite (either Network Activated, or per-site – same error). It’s bad because it then stops you getting back into the Admin interface to deactivate BFA!

Activating plugin on stand-alone seems to be fine.

Thanks for the heads up, both of you. Can you confirm whether this is happening on just multisite, or if it’s happening on single installs for you as well?

i’m single site. i had to disable as like Goz said, it kills entire site. I had to FTP and rename plugin folder to recover the site.

i’ll reinstall in the morning and see if it was just a CDN that was down.

Hmm I edited my OP but I guess it didn’t stick.

I have BFA working fine on a couple of single-install sites, but breaks the multisite site I tested it on.

I receive exactly the same error message as stated in the first post, single site installation. And I haven’t edited that specific site for days.

Hi I’m having the same issue.

I’m using the plugin on a standalone WordPress installation (ie. not Multisite). I was working on the website last night with no issues.

Any idea what changed today? My website uses the icons throughout the design and am supposed to share with the client tomorrow morning.

Fatal error: Call to a member function get_error_code() on a non-object in /home/melissaj/public_html/*************/**********/wp-content/plugins/better-font-awesome/lib/better-font-awesome-library/better-font-awesome-library.php on line 430

Code around line 430

Looks like it has to do with the version update?

/**
     * Output a <select> version selector.
     *
     * @since  0.10.0
     *
     * @param array  $versions  All available Font Awesome versions
     */
    public function version_callback( $versions ) {

        if ( $versions ) {

            // Add 'Always Latest' option.
            $versions['latest'] = __( 'Always Latest', 'bfa' );

            /**
             * Remove version 2.0, since its CSS doesn't work with the regex
             * algorith and no one needs 2.0 anyways.
             */
            foreach ( $versions as $index => $version ) {

                if ( '2.0' == $version ) {
                    unset( $versions[ $index ] );
                }

            }

Also receiving these errors after deactivating or renaming the plugin’s folder name on FTP.

Warning: fopen(/home/melissaj/public_html/URL/SITENAME/wp-content/plugins/better-font-awesome/better-font-awesome.php) [function.fopen]: failed to open stream: No such file or directory in /home/user/public_html/URL/SITENAME/wp-includes/functions.php on line 3879

Warning: fread() expects parameter 1 to be resource, boolean given in /home/user/public_html/URL/SITENAME/wp-includes/functions.php on line 3882

Warning: fclose() expects parameter 1 to be resource, boolean given in /home/user/public_html/URL/SITENAME/wp-includes/functions.php on line 3885

Hi everyone,

Wow, thanks for the widespread heads up. Bottom line, this issue is fixed now with version 1.0.1. Please do update immediately and I’m truly sorry for the inconvenience.

Here’s the explanation of the issue and solution if you’re interested. . .

In a very rare occurrence, the jsDelivr API has been down today. According to Dmitriy from jsDelivr:

We hit a unique Github limit and it broke jsDelivr’s API.

I’ve spend a lot of effort making sure BFA handles errors well, but since jsDelivr API has been so darned reliable, that error check had simple slipped past my radar. Anyhow, the fix is now in place.

As with most error handling for BFA, if something goes wrong, it is smart enough to output the error in an admin notice, and automatically fall back to the included backup copy of Font Awesome. That way, your icons will still render perfectly and you’ll know what the problem is in case I, or you, need to debug.

So while the jsDelivr is down – I was told this would likely be fixed tomorrow – your site will just continue happily using the backup copy. When the API comes back online again, BFA will grab the latest version, cache it away for the allotted amount of time, and proceed on its merry way.

So once again, I can’t thank y’all enough for the group heads up. It’s often the best way for me to figure out what’s going on.

All the best, and please let me know if you have any further issues.
– Mickey

Working now and has a prominent fallback warning at the top of the page.

Good quick fix!

5 Stars for support on a wonderful and free plugin.

I concur with @jeffrey – great responsive support, 5 stars! Fix works well.