Heads Up W3TC breaks pre-minified JS file

  • Tim Reeves

    (@tim-reeves)


    7 months ago

    First of all, many thanks for a great plugin, it does just what I wanted!

    It took me a few hours to find this, so I wanted to share it. W3 Total Cache must not be allowed to minify these two files (exclude them in its advanced settings):

    wp-content/plugins/simple-comment-editing/dist/sce-editing.js
wp-content/plugins/simple-comment-editing/dist/integrations-admin.js

    The former is large, the latter huge, and both are pre-minified but do not have .min in the file name. When they are not excepted, W3TC tries to minify (again) and sadly, truncates src-editing.js to about half its original size. For sure this a problem with W3TC (or its minifier); but the problem is, when “Minify and Combine” is selected, then the truncated file is packaged up with others, and as it runs to a JS syntax error, quite a bit of the frontend stops working )-:

    So this is just a “Heads up” – with one question: Why do you pre-minify? That is probably what is causing the W3TC minifier to stumble. Perhaps it would be enough to put “.min” in the file names?

    Cheers, Tim

Viewing 1 replies (of 1 total)
  • Plugin Author Ronald Huereca

    (@ronalfy)

    @tim-reeves,

    Thanks for that update. I’m sure this will help others.

    The thing about the minified files is that they are more compiled than minified as they come from many sources. Most modern JS is all compiled from sources, mashed together, and then distributed. I’m afraid there’s not much I can do to “unminify” the scripts.

Viewing 1 replies (of 1 total)
  • The topic ‘Heads Up W3TC breaks pre-minified JS file’ is closed to new replies.