• Running the latest development version, after a complete uninstall deleting the configuration file, and re-installing everything is working very good.

    The only exception is that when you enable the browser cache the url’s get what I believe is a query string attached to the end of the pages and posts, except the main page or home.

    They have this structure https://www.domain.com/something/?57543

    How can that be disabled?

Viewing 5 replies - 16 through 20 (of 20 total)
  • Thread Starter Kenneth Poveda Mata

    (@kepoma)

    Good call, I think that is the best way to do it. To send the bug report you go to the support tab of the plugin.

    I bet you did it already, but you can try to disable minify and empty all your caches, then reenable it again and empty all your caches again.

    Close your browser window that is displaying your site, leave one tab open go to google.com or anything else than your site, do shift + crtl + delete and press clear, then visit your site.

    I am guessing you are using firebug to check the components of your page, or use whatever method you used to check how many css you are sending.

    Thanks for letting me know how to submit the bug report (I may not have found it otherwise). I sent it in last night. I also offered to leave it up in the “bugged” configuration so he could see it if that helped him ID the bug.

    I had tried all the standard trouble shooting stuff already (though I had not known the “shift + crtl + delete and press clear” trick before). I am not a REAL web developer so without firebug I would be lost. Anyway, I am pretty sure the glitch is on the developer version of the plugin side.

    Not sure how much a mom blog will interest you but your welcome to check it out if you feel so inclined (lifeatthecircus.com).

    Just an update. I never heard back from the author about the bug fix (which is understandable since I am sure he is really busy with his own life) but for what it’s worth, I had to reinstall the plugin (developer version) for another reason and now it seems to be working correctly. I don’t know if it just took doing a full uninstall and reload or if he/she corrected the bug without letting me know. Whatever the case, It seems to be working now and I am happy about it. Thanks kepoma for your support and to the developer if you did in fact change anything.

    Thread Starter Kenneth Poveda Mata

    (@kepoma)

    Hey there, he is indeed a busy man. He is all over the forums and twitter answering questions and honestly is incredible how many things he tackles with his plugin.

    I think that he pushes updates quite often but in a low profile style, not publicizing them. And sometimes re-installing things from scratch do have a good effect, by cleaning corrupted settings and databases.

    I am happy things are working out for you now, and by the way I did check your blog, you have your hands full ?? in a very good and fulfilling way. I have two kids but they both are teens now, which is another circus ??

    Sorry for the trouble, the feature with the query strings is to allow for the browser cache settings to be changed and for the new policy to be applied to the files without users having to flush their browser’s cache.

Viewing 5 replies - 16 through 20 (of 20 total)
  • The topic ‘W3 Total Cache – Latest development version adding query strings at the end of u’ is closed to new replies.