• c_dilla

    (@c_dilla)


    Hello,

    After upgrading to the latest version of the Twentythirteen template I suddenly started getting ERR_ABORTED 404 (Not Found) on all woff2 files for some reason while loading the Source Sans Pro and Bitter font files. And it makes the site slower than usual as well.

    The MIME types look okay for the server (I’ve tried different types), the woff files are still loading as they should and the woff2 files are there if I check through the file manager. I’ve tried disabling my cache plugin and going through .htaccess and so on but I can’t figure out what the problem is here.

    Anyone have an idea how to solve this before I start removing the font?

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

Viewing 5 replies - 1 through 5 (of 5 total)
  • Kavya Gokul (a11n)

    (@properlypurple)

    Hey @c_dilla! Have you tried rolling your theme back to a previous version to confirm if this is only an issue in the latest version of the theme? It’s also possible that something changed on your host’s end to cause this, but eliminating suspects one-by-one is the best way to pinpoint the actual cause.

    Thread Starter c_dilla

    (@c_dilla)

    Thank you for your reply, I tried eliminating suspects but ended up removing the references to the woff2 fonts instead. I’m still confused about what the problem was with that woff2 file extension when everything else works fine.

    Kavya Gokul (a11n)

    (@properlypurple)

    Thanks for the additional details @c_dilla. Can you share how exactly were you adding the fonts to the theme, so I can try and replicate this on an actual site?

    Thread Starter c_dilla

    (@c_dilla)

    These are the official fonts included in the Twentythirteen theme. You can see them if you go to Appearance->Theme File Editor->Theme Files->fonts->bitter.css, source-sans-pro-plus-bitter.css or source-sans-pro.css.

    Every reference to a woff file in those css files works and every reference to a woff2 gives some sort of 404 error (even though the woff2 files physically exists in the folder). I thought it had something to do with htaccess, some security plugin or the wrong MIME types but I couldn’t figure it out so I just removed the fonts.

    • This reply was modified 1 year ago by c_dilla.
    Kavya Gokul (a11n)

    (@properlypurple)

    Hey @c_dilla! I have tried to reproduce this on a few different setups, but it looks like it’s working as expected.

    Have you tried to confirm this with all plugins deactivated? A plugin like Health check can help with this.

    If you can install plugins, install and activate Health Check. It will add some additional feature under create a new menu position Tools > Site Health.

    On its troubleshooting tab, you can Enable Troubleshooting Mode. This will disable all plugins, switch to a standard WordPress theme (if available), allow you to turn your plugins on and off and switch between themes, without affecting normal visitors to your site. This allows you to test for various compatibility issues.

    There’s a more detailed description about how to use the Health Check plugin and its Troubleshooting Mode at https://make.www.ads-software.com/support/handbook/appendix/troubleshooting-using-the-health-check/

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Error 404 on the woff2 files in latest version of the theme’ is closed to new replies.