4.0.0.0-rc23 Fatal Error

Hi @atyu, sorry this plugin does not yet support multi-site. It’s possible that you’ve experienced it working in multi-site before, but if so, it was lucky. This sounds like the exact kind of scenario where the lack of support for multi-site would be evident. The plugin doesn’t yet know how to cleanup/re-initialize everything in a multi-site aware way. And probably the fact that it had the fatal error in the first place is due to lack of multi-site support.

There’s a feature request open for multi-site support. I just opened the issue for tracking it. I had thought it was already in there from a discussion several months back. Turns out that previous discussion was in a thread on a specific commit. I’ve linked to it from the new Issue to highlight it a bit better–in case you’re interested in reading up on the discussion thus far.

Hi all, FYI – I updated to latest version on a multisite and all worked ok. Guess I was lucky?

@stv11c I’m using Version 4.0.0-rc23 – which are you using?

Yes, probably lucky.

The key difference in 4.0.0-rc23 had to do with handling symbolic Font Awesome version values like “5.x” or “6.x”, which we started using with the roll out of Font Awesome 6.0.0-beta1. Since then, new kits that are created default to version 6.x if your account has beta features enabled, or otherwise, they default to 5.x. You can also lock it to a specific version, like 5.15.3 or 6.0.0-beta1. Previously, this plugin had some validation rules that would have rejected a version option like “5.x”. rc23 now handles those versions appropriately.

So, it’s not really “lucky”, per se, but if you are using a kit without one of those symbolic versions, then you may not have stepped on this particular landmine. Or if you are running with the Use CDN option, you may not have stepped on this landmine.

At least, that’s my educated guess as to what factors would likely be involved in whether one experienced a fatal error in multi-site mode recently.

In fact, at one point, I almost wrote up some documentation to explain how to make it work in multi-site mode, even though it isn’t really designed for that–because it can work in some scenarios. In the end though, it felt too messy and confusing; I didn’t want to invite others into such chaos. So it seems better to just say “not supported” at this time.

I’m curious, @stv11c, whether you’re configured to use a kit or CDN and what version.

@atyu – Yes I am using the latest 4.0.0-rc23 version.

@mlwilkerson – I have two multisites. One is using CDN (Free Icons), and the other is using a Pro Kit. Both are on the 5x latest and I don’t see the 6x beta in the dropdown.

PS. Not related to this multisite issue, but the only thing that isn’t so great when using a Kit, is my clients can click the ‘Get latest kit data’ link which will display the dropdown again and reveal all my other kits available. Maybe to keep this more private, the user needs to ‘Update token’ first before being able to change the Kit?

Regards
Stephan

Workaround: On the “main” site on my multi-site, the Font Awesome plugin works fine and if I clone that site for every new site I need, it works as well. If I create a site on its own – that is where it fails.