Error: 400

  • Resolved jrkp

    (@jrkp)


    5 years ago

    “Error: 400 – File (/home2/xxx/public_html/wp-content/cache/omgf-webfonts/undefined) exists, but is 0 bytes in size. Is allow_url_fopen enabled on your server?”

    Hello, first thank you for the plugin, looks like you’re making life easier for a lot of us. ?? Unfortunately, I’ve some problem and no clue at all in this field.

    My host is bluehost. And after this error I created a php.ini for the website to “allow_url_fopen = On”, but I got the same error again.

    What can I try next?

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    I’ll get back to you ASAP. Someone else reported the same bug, so something might be broken.

    Thread Starter jrkp

    (@jrkp)

    Thank you, looking forward to hearing from you. ??

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Hi!

    This bug has been fixed since v2.1.0. So, please update! ??

    Thread Starter jrkp

    (@jrkp)

    Hi Daan,

    I was very happy to hear from you, unfortunately it shows me still the same Error. I deleted the cache directory and tried again, same result. ??

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Really? Did you try clearing your browser cache? Lots of things changed in the Javascript, etc.

    Thread Starter jrkp

    (@jrkp)

    I cleared the browser cache, still the same result.

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    That’s strange.

    Could you provide more information? Are any files downloaded? Do you have write access to OMGF’s cache directory? What happens if you change the directory to outside the cache-directory?

    Have you checked the PHP error logs?

    Thread Starter jrkp

    (@jrkp)

    I just tried it again without 1 of the fonts and the download part worked. But I need this font, its “Noto Sans JP”.

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Ah, I see!

    The Google Fonts helper API returned one of the font-files as ‘undefined’, which OMGF couldn’t handle, since I didn’t add any error handling for that.

    I did now. ??

    So, please try the latest update and let me know if it works! ??

    Thread Starter jrkp

    (@jrkp)

    Thank you very much, like your plugin a lot. Works very easy and fast! ??

    But for me there is a down side that no one else will have. The Noto Sans JP(japanese) font is so big, that my page became after the first try 3times as big. Even after reducing to just 1 font-weight my page size increased by 1mb.. and my load time became worse..

    ??

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Ouch, that sucks, @jrkp.

    In that case I don’t think self hosting fonts is a solution. Unless you’re on a cdn.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Error: 400’ is closed to new replies.

Tags