@internationaljack Thanks for the report. And yes, I think you’re right. Could you have a look at my reply on a similar support topic here, and let me know what works for you?
@mlwilkerson thanks for the link. I’m surprised that didn’t come up when I searched earlier.
Anyway, adding the “font_awesome_disable_block_editor_support” line to functions.php had no effect.
Downloading the zip from Github and manually placing the svg-with-js.css file seems to have done the trick.
Question: After this manual update, will I need to do anything special when the next proper update rolls out?
In case it helps, here are my answers to the questions you posed to that other poster:
- Yes, it’s intentional. Our webhost is suuuuper focused on security and my superiors like it that way.
- Not really. They did let me add
define('FS_METHOD', 'ftpext'); to wp-config.php so I can update things via browser (with ftp credentials), but that’s all I’m allowed to do.
- Yes, if there’s no other way.
@internationaljack Thanks for the feedback!
I’m surprised that didn’t come up when I searched earlier.
Oh, I had just posted it prior to linking you to it!
adding the “font_awesome_disable_block_editor_support” line to functions.php had no effect
That would only work when using the new pre-release of 5.0.2-1 from GitHub. By your description, it sounds like you tried adding that filter before installing the pre-release. Is that right? If so, then that’s why it didn’t work.
After this manual update, will I need to do anything special when the next proper update rolls out?
When the real plugin version of 5.0.2 is released and becomes available in the WordPress plugins directory, you’d need to install/upgrade to it in whatever way you normally would. You will not need to do anything more with this svg stylesheet, though. It’ll still be there, serving it’s purpose for you after upgrading to the real 5.0.2 plugin.
However, notice that the path to this stylesheet is versioned according to the version of Font Awesome you use, like uploads/font-awesome/v6.7.2/svg-with-js.css. That 6.7.2 is the version of Font Awesome. If you’re using a kit set to 6.x (which uses the latest version 6 at the time of loading), and we release 6.7.3, then you’ll need to manually add uploads/font-awesome/v6.7.2/svg-with-js.css as well. I’d recommend that you lock the version of the kit to a specific version, and then upgrade manually when a new release comes out, so it doesn’t surprise you.
@internationaljack plugin version 5.0.2 has been released, which I think will address the issue here.
