Font Awesome version “5.12.0” is not one of the available versions.

Hi Tobias,

Thanks for the report. Are you still seeing this problem?

If so, when and where you do see the error message?

-mike

Hi Mike,

Yes, I still see this error message. It is displayed hwen I am logged in to the Admin section, as a notice. Also the icons are not being displayed on the front end when I use the dispaly code.

But it is strange, I only have this error on 1 out of my 4 Network sites.

Yes, that’s strange.

My hunch is that there’s something about how WordPress multi-site works that requires that change how we’re caching the metadata about available releases.

But the fact that you’re only seeing the error on 1 of 4 sites is unexpected.

Could you try, on that one site with the error, to just visit the Font Awesome plugin settings page? (And then notice whether 5.12.0 is listed in the versions dropdown?) Simply loading that plugin settings page should cause the plugin to refresh the releases metadata on your WordPress server.

https://nimb.ws/1maGrO

Interesting. Thanks. This is very helpful. I’m sorry that it comes at your expense, but it helps me to better understand the multi-site scenario.

I’m doing some more investigation in the code now.

Another question I have, if you have the time to give it a try: what if you do that same thing on each of the other three sites? Just load that same Font Awesome plugin settings page. (And then go back to this first one).

They all show the same settings as on the problem-site. They do not show the error message though.

When going back to the first site, the problem site, it still shows the same and the same error message.

Are you using Font Awesome Pro on any of the sites?

(I noticed that you had Free selected in the screenshot on the problem-site).

No, only Free is used.

Are you aware of any differences between these sites regarding cache-related configuration, or cache-related plugins?

Hi,

It is the same configurations and plugins for cache handling on all sites.

@tobbecokta would you be able to try a development version in your environment to see if it resolves your problem?

I have a major update to the plugin, planned for release soon, and I’ve had this issue in mind while working on it. I hope it resolves your problem. It would be helpful to get some early feedback, if possible.

Because it’s a major update, though, this new version of the plugin stores settings and things differently in the database and handles conflict detection and resolution different as well. So if you were to give this a try, you should imagine deactivating and uninstalling the current Font Awesome plugin, taking it back to a clean slate, then starting from scratch by installing and configuring this new one. And then, when this one is released, doing it all again to make sure you’re up and running with the new one. It would be some extra effort for sure, and may not be a good idea to try on a production site. But if you’re willing, then it might be beneficial to us both.

Hi,

Sorry for the lack of response from my side. For some reason it is working now, I dont know why though but I am happy!

Thanks for the reply. It’s probably because the data it’s working with is stored in a WordPress transient, which finally expired and allowed the refresh to happen.

And I think the reason it wasn’t working before the expiration might be because of your multi-site configuration.

I have another release of this plugin that I’ve designed to work better with multi-site. Would you be willing to give it a try, or would you prefer to leave things as-is for now?

Ok i understand.

As it is working as it should now I keep it as it is, thanks!