• Resolved infosws

    (@nicksws)


    Hello,

    Issue with WooCommerce versions 8.5.0, 8.5.1, 8.5.2 & W3 total cache version 2.2.0 – 2.6.1

    I have an issue where a WooCommerce js file is coming up with 500 Internal Server Error when its minified using W3 total cache. I have this issue on two separate websites running on different servers.

    While attempting to debug the issue, in the browser console I see:

    https://xxxxx/wp-content/cache/minify/d0546.js was loaded even though its MIME type (“text/html”) is not a valid JavaScript MIME type – trying to visit this url directly to inspect it comes up with internal server error (500).

    Uncaught SyntaxError: expected expression, got ‘<‘ – This references the d0546.js file which i’m unable to view.

    I tried to view this file directly via ftp and it does not exist.

    I switched the theme to storefront and deactivated other plugins leaving just WooCommerce 8.5.2 and W3 total cache 2.6.1 the issue persisted.

    I rolled back W3 total cache to several previous versions ( oldest 2.2.0 ) and the issue persisted.

    I rolled WooCommerce back to 8.4.0 and the issue disappeared, versions 8.5.0, 8.5.1 and 8.5.2 this issue comes back.

    I tried another minification plugin ( Autoptimize ) and did not experience this issue with WooCommerce 8.5.2 so it seems to be W3 total cache specific issue.

    It doesn’t seem like a w3 total cache issue because rolling the plugin back to previous versions should of cleared the issue.

    If you need anymore info please let me know but it seems like a change made in WooCommerce 8.5.0 + causing the problem.

    Can you fix this please?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Shameem a11n

    (@shameemreza)

    Hi @nicksws,

    Have you had a chance to disable the Order Attribution feature? You can find it under WooCommerce > Settings > Advanced > Features. After disabling it, check if it resolves the issue.

    Let us know how that goes. Looking forward to helping you.

    Thread Starter infosws

    (@nicksws)

    Hi @shameemreza,

    Turning off this option seems to solve the problem on one of the installations i’ve been having this problem on. I’ve managed to turn on the minification once more and do not see this error anymore.

    I’ll test this on the other website that i was having this issue on and get back to you.

    Thanks!

    Plugin Support Shameem a11n

    (@shameemreza)

    Hi @nicksws,

    I’m glad to hear that disabling the Order Attribution feature has resolved the issue on one of your installations. Trying the same on the other website where you’re experiencing the issue is a good step.

    Once you’ve done that, please do let us know the results. If the problem persists, we’ll be more than happy to assist you further.

    Looking forward to your update.

    Thread Starter infosws

    (@nicksws)

    Hi @shameemreza,

    I’ve now tested this on the other website and I get exactly the same result.

    I turn the Order Attribution feature off and i’m able to reactivate the W3 Total Cache js minification.

    I guess this means there is a conflict with this feature and W3 Total Cache js minification. I did roll back W3 total cache multiple versions and it appears like they have made no changes.

    As i said before websites using autoptimize for js minification do not get this error with this feature.

    Hope this helps

    Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hi again @nicksws

    It does seem like there might be a conflict between the Order Attribution feature and the W3 Total Cache JS minification. This is not uncommon, as plugins can sometimes interfere with one another’s functionality.

    As an alternative, I would suggest trying to use another plugin for JS minification like Autoptimize as it seems to be working well with the Order Attribution feature on your other websites.

    I hope this.

    Thread Starter infosws

    (@nicksws)

    Hi,

    We’ve had this problem on another install with these two plugins.

    Autoptimize is a great plugin but we use W3 Total Cache for the complete system and would much prefer it works correctly with W3.

    So we will be disabling this feature by default on all installs and will wait for this to be fixed.

    Plugin Support Shameem a11n

    (@shameemreza)

    Hi @nicksws,

    I’m glad you were able to find a solution to your inquiry here and thanks for sharing it with the community too! 🙂

    I will mark this thread as resolved. Should you have further inquiries, kindly create a new topic here.

    Thanks!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Js file 500 Internal Server Error when minified w3 total cache’ is closed to new replies.