• Hello,

    our website is currently a bit slow which is probably due to the following error.

    This message is displayed in the CMS.
    _________
    Better Font Awesome

    API Error
    The attempt to reach the jsDelivr API server failed with the following error: http_request_failed: cURL error 7: Failed connect to api.jsdelivr.com:80; No route to host (URL: https://api.jsdelivr.com/v1/jsdelivr/libraries/fontawesome/?fields=versions,lastversion)

    Don’t worry! Better Font Awesome will still render using the included fallback version:

    Solution
    This may be the result of a temporary server or connectivity issue which will resolve shortly. However if the problem persists please file a support ticket on the plugin forum, citing the errors listed above.
    _________

    Is the error corrected automatically?
    Or do I have to do something?
    Status as of 05.05.2020

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 17 total)
  • Same problem here.

    OK, I think I solved the problem.
    In the file:
    wp-content\plugins\better-font-awesome\vendor\mickey-kay\better-font-awesome-library\better-font-awesome-library.php

    Change / comment out line 238 from
    $this->setup_api_data();
    to
    //$this->setup_api_data();

    Thread Starter valerio80

    (@valerio80)

    However, this will cut the connection to the Better Font Awesome server. Shouldn’t be a permanent solution either, should it?

    Hi there, I am facing the same problem. Loading the site takes a good 5-10 seconds longer. When de-activating the plugin, the site loads immediately but of course then the icons are gone.

    But thanks to xberg’s solution it works fine again ??

    • This reply was modified 4 years, 8 months ago by Ryter8.

    i have same problem
    API Error
    The attempt to reach the jsDelivr API server failed with the following error: http_request_failed: cURL error 28: Connection timed out after 10000 milliseconds (URL: https://api.jsdelivr.com/v1/jsdelivr/libraries/fontawesome/?fields=versions,lastversion)

    Don’t worry! Better Font Awesome will still render using the included fallback version: 4.7.0

    Same here. But xberg’s solution helped me out. Thanks!

    Thanks @xberg for your fix ??

    same problem here, and the commenting out fix worked. still, not happy with manual code changes to the plugin. please fix and release an update asap! thanks!

    • This reply was modified 4 years, 8 months ago by sezgee.

    Same here, it looks like a temporary connection / routing problem.
    From my office and servers I can’t reach the jsDelivr api url, from my home or my mobile phone no problems at all…

    Yes, it works! Thank you so much. Super easy fix. Though I do wonder of the implications and long-term fix, too. All good for now, though ??

    Also having this issue.

    http_request_failed: cURL error 28: Connection timed out after 10001 milliseconds (URL: https://api.jsdelivr.com/v1/jsdelivr/libraries/fontawesome/?fields=versions,lastversion)
    
    Don't worry! Better Font Awesome will still render using the included fallback version: 4.7.0

    Judging by the OP’s post time, 5hrs is considerably long time for a connection problem. Probably time for me to look at an alternative plugin. What’s more, not sure if its related, but my site load time has gone to over 20 seconds, not sure if anyone else has seen a spike in load time because of this. Disabled the plugin and load time rapidly increased.

    • This reply was modified 4 years, 8 months ago by mburdett555. Reason: definately slow page load times due to connection error in this plugin

    Is anyone else also seeing a fatal error if you go to Settings > Better Font Awesome?

    *EDIT* After commenting out that line

    @burlingtonpress out of the box, commenting out that line throws an error yeah
    PHP Fatal error: Uncaught Error: Call to a member function get_error_code() on string in ……
    Best not to edit plugin files directly anyway, seems to be working ok now so can revert code changes

    @mburdett555 Oh I hate editing plugin files, but not as much as I hate a site that isn’t functioning properly because of a plugin. ??

    @burlingtonpress Did you check the apache error log? Theres a function that can also be edited out, and theres an else statement somewhere else.
    I commented out the whole function that ends on line 531 of the same file, and the else statement on 554 and the site seemed to work again

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘Better Font Awesome API Error’ is closed to new replies.