Viewing 8 replies - 1 through 8 (of 8 total)
  • Hello athleticcity,

    Thank you for contacting WooCommerce support.

    I tried to access your website but could not access it due to some restrictions.
    Could you make your website accessible so I can check the issue?

    Looking forward to your response. ??

    Thread Starter athleticcity

    (@athleticcity)

    Hi Zubair,

    I have lifted the restrictions. Should work for you now.

    Thanks

    Hi @athleticcity,

    I also tried viewing your store but still facing a similar issue with Error?1005 as earlier shared with my colleague above. I enabled a VPN but got this screen instead:

    Looking at the shared description, it seems that the fonts star.eot and WooCommerce.eot are not being found because they might not be located in the specified URL. I understand you already went ahead and switched to a different theme and the issue does not persist.

    When switching to a new theme, do you disable any of your active plugins? The reason why I’m asking this is because, it could be possible one of your plugins could be causing this issue. Did you already have the chance to disable all plugins and enable them one at a time to see which plugin will start displaying the error once activated?

    This way, we can be able to eliminate a possible plugin conflict.

    Please try this and let us know how this goes.

    Thread Starter athleticcity

    (@athleticcity)

    Hi, ckadenge,

    I have lifted the restrictions for your ASN. Should work for you now.

    1. I swiched off all plugins. Only Storefront Theme is active. Result: There is no font-face.
    2. I only switch on the woocommerce plugin. Result: woocommerce/assets/fonts/star.eot and woocommerce/assets/fonts/WooCommerce.eot are still there in the font-face.
    3. I checked the woocommerce plugin via ftp. In the folder plugins > woocommerce > assets >fonts is not a star.eot or WooCommerce.eot file. All other files the font-face want have are in this folder.

    Any Idea?

    Thanks

    Hi @athleticcity,

    Thanks for your patience in troubleshooting this issue so far. It seems that WooCommerce is still attempting to load fonts that aren’t actually present in the woocommerce/assets/fonts/ directory, resulting in the 404 errors you’re seeing.

    This issue likely stems from cached or residual CSS code within WooCommerce that is trying to call these fonts even though they aren’t present. Here are a few steps you can try to resolve this:

    1. Clear Caches: If you have any caching plugin or server-side caching enabled, try clearing it to ensure that no outdated CSS or cached assets are being loaded. This may help remove any cached references to star.eot and WooCommerce.eot.
    2. Check WooCommerce and Theme Versions: Ensure that your WooCommerce and Storefront Theme are up to date, as font-related issues can sometimes be resolved in newer releases. You can check for any available updates directly in your WordPress dashboard under Dashboard > Updates.
    3. Clear transients: To do this, go to WooCommerce > Status > Tools and you’ll find Clear transients button in front of WooCommerce transients as well as Expired transients. Click on both.
    4. Custom CSS Removal (If Applicable): If you have any custom CSS that references these fonts, try temporarily disabling it to confirm it’s not affecting the font loading.
    5. Reinstall WooCommerce: As a final step, if the above steps don’t work, try reinstalling WooCommerce. Before doing so, make sure to back up your site to prevent any data loss. Reinstalling the plugin can refresh any missing files or references, potentially clearing up this issue.

    Please give these steps a try and let us know how they work out. We’ll be happy to continue assisting if the issue persists.

    For the last step though, please be sure to take a backup of your website before uninstalling and reinstalling WooCommerce.

    Thread Starter athleticcity

    (@athleticcity)

    Hi,

    I downloaded the latest version of storefront to my computer.

    In storefront > inc > woocommerce > class-storefront-woocommerce.php line 101:

    public function add_core_fonts() {
    $fonts_url = plugins_url( '/woocommerce/assets/fonts/' );
    wp_add_inline_style(
    'storefront-woocommerce-style',
    '@font-face {
    font-family: star;
    src: url(' . $fonts_url . 'star.eot);
    src:
    url(' . $fonts_url . 'star.eot?#iefix) format("embedded-opentype"),
    url(' . $fonts_url . 'star.woff) format("woff"),
    url(' . $fonts_url . 'star.ttf) format("truetype"),
    url(' . $fonts_url . 'star.svg#star) format("svg");
    font-weight: 400;
    font-style: normal;
    }
    @font-face {
    font-family: WooCommerce;
    src: url(' . $fonts_url . 'WooCommerce.eot);
    src:
    url(' . $fonts_url . 'WooCommerce.eot?#iefix) format("embedded-opentype"),
    url(' . $fonts_url . 'WooCommerce.woff) format("woff"),
    url(' . $fonts_url . 'WooCommerce.ttf) format("truetype"),
    url(' . $fonts_url . 'WooCommerce.svg#WooCommerce) format("svg");
    font-weight: 400;
    font-style: normal;
    }'
    );
    }

    I delete the lines:

    src: url(‘ . $fonts_url . ‘star.eot);
    url(‘ . $fonts_url . ‘star.eot?#iefix) format(“embedded-opentype”),

    src: url(‘ . $fonts_url . ‘WooCommerce.eot);
    url(‘ . $fonts_url . ‘WooCommerce.eot?#iefix) format(“embedded-opentype”),

    Now the error 404 is gone!

    So the Theme tries to load URLs that don’t exist in the Woocommerce plugin.

    As I already wrote, there is no star.eot or WooCommerce.eot file in the “plugins > woocommerce > asset >fonts” folder.

    To me it looks like this is the error of the Theme and not the error of my installation or a Cache problem.

    Or?

    Thanks!

    Hi there,

    This is indeed a bug with Storefront. I reported the issue here: star.eot and woocommerce.eot fonts don’t exist anymore.

    Thanks for spotting this, the team responsible should pick this up and will hopefully be fixed in an upcoming release of Storefront.

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