TypeError: e.response undefined

With 4.0.0-rc12 everything works fine.

Do you have any cache settings or plugins enabled?

ok let me try with wp rocket dissabled

Same.

I’ve released 4.0.0-rc16 which I expect to solve the upgrade problem. I also addressed the issue that the revslider plugin appeared to be complaining about regarding admin_notices. It seems that plugin made some invalid assumptions about the type of callbacks that might be used for action hooks. I’d used a valid type (a closure), but revslider choked. I’ve compromised and moved away from using closures in that case (and several others, just in case).

With the latest release the plugin is working except the scanner part. I click to start the scanner, the window comes up but it does not seem to be logging anything. is there a way i can check that its in place?

Side note: I still have the REST API issue due to the USERPRO plugin, which i am also pretty confident is also the reason for my Font Awesome conflict. Notified the developer. waiting on a response.

Scratch that. When trying to save, it gives the green checkmark that it saved but reverts to the previous settings and i see this error in the console.

View post on imgur.com

Ok, now we’re getting somewhere. I think it’s pretty safe to say that whatever is breaking the REST API (such as the known problem with USERPRO) is making it impossible for the browser to communicate with the WordPress server on the Font Awesome REST API endpoints.

I think that until that is resolved, there’s not much more that could be done using this Font Awesome plugin, which is a sad loss. I’ve added quite a bit of extra error handling to try and work around some of the noise that other buggy plugins or themes might introduce, but I doubt this is something I’d be able to work around, if the REST API is rendered non-responsive.

So if it’s important for you to have your icons working, and it’s important to continue using USERPRO, and its REST API problem isn’t resolved soon enough for you, you could attempt a custom WordPress setup of Font Awesome.

That approach would allow you to set up whatever version of Font Awesome you want to use without a plugin. There’s even guidance in those linked docs for manually running the conflict detector and making use of its results to try and remove those other conflicting versions of Font Awesome that you know are lurking.

This is only recommended if you’re comfortable doing things like editing your theme’s functions.php. It’s a lot of extra effort, but it may be worth it in this case. You’re unfortunately in one of the Total Chaos? scenarios here: multiple plugins breaking one another and suspending the known physical laws of the universe.

Quick Update. I was able to solve my font awesome conflict. I did edit my functions.php and blocked the calendar plugin from enqueuing its version of font awesome. It was loading from a kit.

I am still waiting to hear back from the dev on the UserPro plugin about the api issue.

Thanks for all the help so far.