• Resolved Michael Samson

    (@illuminice)


    Hello,

    I’ve been dealing with a nightmare of issues here related to using the CSS/JS minification and needing the query strings to function.

    I found this thread which explains much of what is going on:
    https://ww.wp.xz.cn/support/topic/query-string-not-added-to-minified-css-js/

    I’ve been encountering all of the same problems, and a few others as well. This is clearly NOT solved!

    Here is what I am seeing:

    1. If you enable HTTP2/push, you end up getting the files served twice. One file has the query string, and the other doesn’t. This actually prevents the query strings from working, and also kills the score in GTmetrix. When you turn the HTTP2/push off, this results in no query strings being on the files at all.

    2. Turning off the Rewrite URL Structure actually allows the query strings to work, but this results in excessively long load times for some reason. I’ve seen load times as long as one minute when turning off this feature. This seems to be a problem unto itself.

    3. Turning off the HTML minification also results in the query strings working again, but then you have to give up the HTML minification which isn’t good. I’ve also observed excessively long load times when turning this feature off.

    …..

    I’m at the point here where I am about to give up on minification completely, which is unfortunate. I’ve put so much time into this already, and I really wanted to get it working properly. But after extensive testing of the various options and combinations you can use them in, it became apparent to me there are some serious bugs.

    I’m bringing this to your attention again so it will maybe get fixed. The thread I mentioned above is from nearly a year ago. I think it’s time you figure this out.

    Hope this helps!

    ~ Michael

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

    (@vmarko)

    Hello @illuminice

    First of all, I am sorry about the issue you are experiencing, and thank you for taking the time to report this issue.
    And yes your statements are correct and we do have an open issue in our Github repository for this.
    Please, feel free to comment on the issue and add any more information to help us fix the issue.
    Due to some other more urgent issues, this one was not fixed and the developers are working on a fix for future releases.
    Once again, thank you for reporting this and please make sure to track the progress of the issue regularly.
    Thank you!

    Thread Starter Michael Samson

    (@illuminice)

    Hi Marko,

    Unfortunately this has cost me days of work, and we are now completely abandoning this effort. I’m about to dismantle our Redis cluster since it was only being used for the minification.

    To be completely frank, this is a serious issue that affects one of the most used features of this plugin. I think it’s a bad sign that this has been known about for nearly a year, and is still not fixed. A year is a very long time to have a known issue.

    Also, I find it strange you set these threads as Resolved simply because you wrote back. This is obviously not resolved.

    In any case, I’m not going to be trying this again. It’s simply not worth all the potential problems.

    We’re using W3 Total Cache for the browser caching, but that’s all. I do hope you get this fixed for your other users.

    All my best,

    ~ Michael

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @illuminice

    Once again thank you for taking the time to report the issue.
    We are working on a fix and it will be done for future releases.
    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Multiple Bugs Affecting Query Strings for CSS/JS’ is closed to new replies.