• Resolved xorinzor

    (@xorinzor)


    WordPress: v6.2.2
    W3TC: v2.7.6

    When enabling CSS minify or combine, the path to fonts (in my case specifically the font faces by WooCommerce) are wrong.

    Instead of “wp-content/plugins/woocommerce/assets/fonts/star.eot” (and other variants) it turns it into “content/plugins/woocommerce/assets/fonts/star.eot”, which obviously doesn’t exist and thus returns a 404. If I add the font-face to my theme CSS it results in the same problem.

    Tried switching between the default and “CSS Tidy”, but both result in the same output.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @xorinzor

    Thank you for reaching out and I am happy to help!
    I am not sure on where the WP is actually isntalled so this may be the problem of a custom path
    In this case, please try to enable the option “Fix document root path” in Performance>General settings>Miscellaneous, save all settings and purge the cache and let me know if it helps!

    If possible share the website URL

    Thanks!

    Thread Starter xorinzor

    (@xorinzor)

    Hi @vmarko, thanks for the quick reply!

    The website is not yet public, as such I cannot share a URL yet.

    I checked the configuration, but it appears W3TC already correctly detects the document root, nonetheless I did try it, but unfortunately it resulted in the same problem.

    Forgot to mention, I am using the bitnami wordpress helm chart (which in turn uses the “bitnami/wordpress” docker image). Which might aid in troubleshooting this issue.

    I just now tried enabling debug mode, which interestingly enough results in a path of “../../../../../../../plugins/woocommerce/assets/fonts/star.eot”


    EDIT: turns out that’s because with debug mode it didn’t edit the path anymore, but the original source was: “/wp-content/themes/astra/assets/css/minified/compatibility/woocommerce/woocommerce-grid.min.css”

    I’m going to dig a little deeper here and will update with my findings, feel like the theme might be part of the issue here.

    • This reply was modified 1 month, 3 weeks ago by xorinzor.
    Thread Starter xorinzor

    (@xorinzor)

    I simply added it to the list of exclusions, seems like the fastest fix.

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