Plugin broke after 5.0.1 update

  • We get a message in WP admin that says:
    Failed to determine Font Awesome version when setting up self-hosted assets.

    Now the icon button to add icons doesn’t work anymore.

    Please advice.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter ridle

    (@ridle)

    Also some console log info:

    stack trace: 0 /public_html/inhoud/plugins/font-awesome/includes/class-fontawesome-svg-styles-manager.php(223): FortAwesomeFontAwesome_SVG_Styles_Manager->selfhost_asset_full_path() 1 /public_html/inhoud/plugins/font-awesome/includes/class-fontawesome.php(1042): FortAwesomeFontAwesome_SVG_Styles_Manager->is_svg_stylesheet_present() 2 /public_html/inhoud/plugins/font-awesome/includes/class-fontawesome.php(386): FortAwesomeFontAwesome->initialize_admin() 3 /public_html/inhoud/plugins/font-awesome/font-awesome-init.php(71): FortAwesomeFontAwesome->init() 4 /public_html/inhoud/plugins/font-awesome/font-awesome.php(207): require(‘…’) 5 /public_html/wp-includes/class-wp-hook.php(324): FortAwesomeFontAwesome_Loader->init_plugin() 6 /public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 7 /public_html/wp-includes/plugin.php(517): WP_Hook->do_action() 8 /public_html/wp-settings.php(704): do_action() 9 /public_html/wp-config.php(218): require_once(‘…’) 10 /public_html/wp-load.php(50): require_once(‘…’) 11 /public_html/wp-admin/admin.php(34): require_once(‘…’) 12 /public_html/wp-admin/edit.php(10): require_once(‘…’) 13 {main}

    edit.php?post_type=page:897 php version: 8.3.13
    WordPress version: 6.7.2
    multisite: false
    is_network_admin: false

    Plugin Author mlwilkerson

    (@mlwilkerson)

    @ridle Thanks for the report.

    That particular problem appears to be caused by some unexpected options data for the plugin in your WordPress database. While the error is thrown by some of the new code for the block editor support, it would be caused when the plugin can’t figure out what version of Font Awesome you’ve configured to use.

    That’s a more fundamental problem that would impact other features of the plugin as well. It might occur when the state of the plugin’s options in the database gets corrupted somehow, maybe doing some kind of database migration or backup/restore that went awry.

    It may resolve the problem to simply re-save the plugin’s options. If you’re in “Use CDN” mode, you could select a different version, save, and then re-select whatever version you had before, and save again. Of if you’re in “Use Kit” mode, you could “refresh kits”, pick a different kit, save, then go back and pick your original kit and re-save.

    If that doesn’t work, then it may be necessary to do a deeper clean of the plugin’s state in your WordPress database. The easiest way to do that is to deactivate and uninstall the plugin (using the controls in the plugins dashboard, so the plugin’s cleanup code runs). Then re-install and re-activate.

    Try one of those and let me know?

    Thread Starter ridle

    (@ridle)

    While this DOES get rid of the message, the buttons still doesn’t work sadly.

    I also reinstalled the plugin from scratch.

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