Font Awesome fatal error

Thanks for the report.

In which version of the plugin are you seeing this error?

Do you know which version of the plugin had been running successfully before the migration?

Are you using WordPress multisite?

The fact that it was migrated makes me think that there may be some mismatch between the version of the plugin you’re running and the format of the options in the database. There was a change in the options format recently. The plugin automatically handles that migration upon upgrade. But it seems possible that if something happened out of the expected order due to a site migration, that could undermine the automated update.

However, if you’ve deactivated, uninstalled and set it up fresh on the new site and that still doesn’t resolve the problem, then that makes me wonder if you’re using multisite. (The plugin doesn’t yet support multisite, and this is the kind of error you might see in some cases when running it in multisite mode.)

Finally, do you have access to either the WP CLI or direct database access? If so, we could inspect the values of the relevant database options.

Another question: where the plugin error message indicates “Try deactivating, uninstalling, and re-activating the Font Awesome plugin” you said you’d tried that a couple of times already.

But could you be more specific about what steps you took to uninstall?

In particular, it’s important that for the “uninstall” instruction that you click the “Delete” link on the plugin’s entry on the plugins page. That’s what causes the plugin’s uninstall logic to be executed, which includes deleting all of its entries in the database, so that they might be initialized from scratch upon a fresh new activation.

While activated it looks like this in the plugins listing. The “Deactivate” link is available:
https://www.evernote.com/l/AAcPrSKwsdFC_pGLhSKVQVOoQO7z6xKpnCQ

When the plugin is deactivated, the “Delete” link is available:
https://www.evernote.com/l/AAde0f0HNbtLjZPVCESmcL-42U5yCVNdKLQ

So one thing I’m curious about is whether there remains some old data in there even after clicking “Delete” to uninstall. The other thing I’m curious about is: if there is old data in there, what’s in there that’s invalid?

To inspect what may be in there now, if you have access to the wp cli, you could do this:

wp option get font-awesome

It would be helpful to me to know what values are in there.

Privacy Caveat: if you have a kitToken in there, that’s not really a secret, since it’s used as part of the kit embed URL that’s loaded in your public web page sources that use the kit, but it does identify a particular kit of yours, so you may not want to paste it here. All I care about for this investigation is whether it’s NULL or not NULL.

When you first activate the plugin, it should get the default configuration, which would look like this:

array (
  'usePro' => false,
  'compat' => true,
  'technology' => 'webfont',
  'pseudoElements' => true,
  'kitToken' => NULL,
  'apiToken' => false,
  'dataVersion' => 4,
  'version' => '5.15.4',
)

If you don’t have access to use wp cli, you could query the database directly, on the wp_options table, where the option_name is font-awesome. What’s in the option_value field? (It’ll have the same content, in a different format–so don’t paste it in here with a kitToken if you don’t want to disclose that.)

a:8:{s:6:"usePro";b:0;s:6:"compat";b:1;s:10:"technology";s:7:"webfont";s:14:"pseudoElements";b:1;s:8:"kitToken";N;s:8:"apiToken";b:0;s:11:"dataVersion";i:4;s:7:"version";s:6:"5.15.4";}

I’m especially curious if you somehow got the options set to use Pro CDN with v6 before upgrading to plugin v4.1.0 or newer. That would be invalid, and the new versions of the plugin would never let you save those invalid options. But perhaps you set those with an old version of the plugin, then migrated, then upgraded, and then somehow your attempt to uninstall left those old, invalid option values in the db.

To manually clear out the relevant data in the database in order to get a fresh activation:

With the wp cli:

wp option delete font-awesome

and

wp option delete font-awesome-releases

Or directly in the database, delete the rows in the wp_options table where the option_name is font-awesome or font-awesome-releases.

(There are a couple of other things stored in the database, but this should be more than enough to ensure a clean, fresh new activation.)

After you’re sure those have been removed, you could try to activate the plugin again. This would re-initialize everything with the default options. I would expect everything to work fine from there.

great!