• Resolved zaist

    (@zaist)


    Hello there,

    Since updating to 5.0.1 we got an error message in the admin page :

    The Font Awesome plugin caught a fatal error.
    Failed to initialize filesystem usage for creating self-hosted assets. Please report this on the plugin support forum so it can be investigated.

    What can we do to solve this ?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author mlwilkerson

    (@mlwilkerson)

    @zaist Thanks for the report. This error probably happens because you have your system locked down to disallow access to the filesystem. Does that sound correct to you?

    I’m working on a 5.0.2 update to help address this issue. If you’re willing to live on the edge, you could download the font-awesome.zip attached to the GitHub Release here. It will show you a warning explaining how to manually put the required svg stylesheet where it needs to be.

    Or if you do not use the Block Editor, with that pre-release installed, you can add this to your theme’s functions.php or equivalent:

    add_filter( 'font_awesome_disable_block_editor_support', '__return_true' );

    If living on the edge doesn’t work for you, then downgrading to plugin version 4.5.0 until this new release is published is probably your best bet.

    Either way, I’m curious about your scenario. Understanding it better could lead to better solutions. Could you tell me more about it?

    1. Have you intentionally restricted access to the filesystem on your WordPress site? Or it this perhaps a constraint added by your hosting provider?
    2. Do you have the capability of making exceptions to this constraint, when you know something is safe?
    3. Does it work for you to manually place the required file in the required place if prompted to do so?
    Thread Starter zaist

    (@zaist)

    Hi @mlwilkerson ,

    So I went bleeding edge and wgeted the file in place. It now works.
    As of you other questions, I am glad to help out as much as I can.
    1. Our site is self hosted and I want to only update plugins via SSH (SSH SFTP Updater Support). I don’t like the idea of having a FTP service open and exposed.
    2. I could. Lately I stumbled on many plugins issues regarding direct access.
    3. It works yes.

    Plugin Author mlwilkerson

    (@mlwilkerson)

    Thank you. I appreciate the feedback!

    I upgraded Font Awesome to 5.0.1 which was working well, however with the upgrade, during installation, I got the following error: The Font Awesome plugin caught a fatal error.

    I downloaded version 5.0.2-1, but I still get the same error, where can I get the privies version before 5.0.1 so I can use this version which worked well?

    Plugin Author mlwilkerson

    (@mlwilkerson)

    @ci458203 You can download version 4.5.0 by going to the Advanced View on the plugin’s directory page, scroll down to “Previous Versions”, and select a previous version from the dropdown. You can then install that version in the WP admin by doing “add new plugin” and “upload”, providing that downloaded zip file.

    As another possibility, there’s also another pre-release of 5.0.2-2 which may be helpful.

    I don’t know what problem you’re experiencing, though, so I don’t know whether that pre-release will make any difference for you. If you’d like to report your problem, could you open a new support topic in this forum and describe your scenario?

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.