Support » Plugin: Better Font Awesome » [Beta Test]

  • Resolved Daniel McClure


    Does installation go smoothly?
    500 Error the first time, but I deactivated and re-activated and was fine so probably just a server gremlin.

    Is your previous Font Awesome version selection preserved?
    Latest – Yes.

    Are you able to select versions greater than 5?
    Are you able to update and revert versions without issue?

    Yes, tested all and verified in source.

    Are all of your icons still properly showing on the frontend?
    As far as I can tell.

    Are legacy icons being correctly auto-mapped to their newer versions (see the list of updated icons)?

    Anything else you notice?
    “Remove existing Font Awesome” doesn’t remove from “easy-social-share-buttons3

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Mickey Kay


    Thanks Daniel, very much appreciate the testing. Two questions for you:
    1. by any chance do you have access to your error logs (curious if that 500 was something related)?
    2. any idea if the easy social share buttons issue was around before as well (this update doesn’t impact that part of the functionality at all)?

    Thanks again!

    1. Can’t see it in the logs for some reason.

    2. Yes, it was like that before.

    Tried the beta on a new site on a different server where it had never been installed and got the 500 error too. I’ve replaced identifying details but the rest is as is:

    Here is my log:

    [php7:error] [pid *] [client *] PHP Fatal error: Uncaught Error: Cannot use object of type WP_HTTP_Requests_Response as array in /var/www/\nStack trace:\n#0 /var/www/ Better_Font_Awesome_Library->get_icon_array_version_5()\n#1 /var/www/ Better_Font_Awesome_Library->get_icon_array()\n#2 /var/www/ Better_Font_Awesome_Library->setup_stylesheet_data()\n#3 /var/www/ in /var/www/ on line 874, referer:

    Plugin Author Mickey Kay


    Thanks Daniel, this was super helpful. I was able to reproduce this error, which resulted from an edge case where a stored transient value did not match value fetched from the API.

    Anyhow, I just pushed v2.0.0-beta3, which should resolve the issue. If you’re willing, I’d love for you to take it for another test spin:

    Thanks so much for your help!

    Daniel McClure


    Didn’t dig as deep this time but first impressions are everything is working as expected on a new install.

    Daniel McClure


    Just wanted to confirm another successful install of beta3.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘[Beta Test]’ is closed to new replies.