• Hello everyone can you please help me? I am really not very coding literate and I have been working with some developers for several months to get some customized work done on my theme. Everything was working pretty well until a couple of months ago when we ran into a problem where “query string parameters are being stripped”.
    -We turned off all caching
    -host checked and confirmed there is nothing they’re doing to cause this
    -Sucuri says you can’t turn off their caching for certain static assets like javascript, but they were able to show that they are not the problem.
    -we tried disabling all plugins and updating everything.
    -checked the htaccess file for caching.
    -The only thing left that I can think of right now is that I used WP Super Minify a couple months ago….maybe that could have done something?
    This is the best summary that my developer has sent me:

    “Wow, just tell them to view source of home page and search for “.js”. You will notice that query parameters are missing for all occurrences. Same is the case for .css resources.
    Tell them that parameters are being added in the enqueue methods. Here is a screenshot for reference -> https://prntscr.com/kbsecc. While they are removed on front-end. Here is a screenshot for reference -> https://prntscr.com/kbseub.”

    I don’t know but my host has given up, sucuri has given up, and it sounds like my developers are thinking about throwing in the towel too.
    Anybody have any ideas? ??

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 18 total)
  • Thread Starter joeborders

    (@joeborders)

    The last thing that was suggested to us by our host was to update WPBakery, which seemed to have an outdated javascript composer….compiler? We did that and its still messed up ??

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    >> he only thing left that I can think of right now is that I used WP Super Minify a couple months ago….maybe that could have done something? <<

    What happens when you remove that plugin?

    Thread Starter joeborders

    (@joeborders)

    I removed it and its still a problem. Thats the thing. I used the plugin kind of unconventionally. Basically any time I made major changes to the site I turned it on for a bit and then deactivated it….thinking it had done its job

    Thread Starter joeborders

    (@joeborders)

    but I dont know if its effects linger after its uninstalled

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    What happens if you disable the Sucuri CDN and allow direct access to your site?

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Also, check your Sucuri settings. By default, it removes query strings:

    See https://i.imgur.com/lpQRMmL.png

    Thread Starter joeborders

    (@joeborders)

    I’ve disabled the Sucuri CDN, but sucuri says that you cant turn off caching of certain static assets like javascript. They gave me a link to clear the cache though and its still a problem :-(….I can’t find the area you’re refering to in your picture. and the internet says that section that you’ve circled is just for hiding the wordpress version?

    Thread Starter joeborders

    (@joeborders)

    here’s what they said about this:
    The firewall isn’t capable of filtering out query strings out of your code as it is loaded. These query strings are hardcoded inside your actual website code, the firewall would have to be able to dynamically read through your code as it reads the response from the hosting server and filter them out. Which it is not, it is simply not capable of doing this.

    To demonstrate that the firewall isn’t doing this, I have used a technique here to connect directly to your hosting server: https://kb.sucuri.net/firewall/Troubleshooting/bypassing-the-proxy-for-testing-and-development
    I recommend asking your developers to use that technique if they believe the firewall is responsible since this will bypass the firewall and they can indeed check if the firewall is responsible.

    Here are my findings, the code on the hosting server doesn’t contain any query strings:
    So the firewall isn’t filtering anything out or performing any caching, the code is simply missing the query strings.

    • This reply was modified 6 years, 7 months ago by joeborders.
    Thread Starter joeborders

    (@joeborders)

    I don’t know very much at all about coding, but we can see the correct code on the server.

    Thread Starter joeborders

    (@joeborders)

    The host confirmed that the correct code is not being shown and advised I update my plugins and try disabling all plugins. Neither of these things solved it. ??

    Thread Starter joeborders

    (@joeborders)

    …is there a way to change which functions.php is loaded in a theme? we have a child theme and a child theme 1.0 i am seeing the code we need in child theme, but it is loading like it is in child theme 1.0…….could the site maybe be loading the wrong functions.php?

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    When you have a child theme, functions.php is loaded in addition to the parent’s functions.php. (Specifically, it is loaded right before the parent’s file.)

    Thread Starter joeborders

    (@joeborders)

    but is there a way to define what functions.php file is loaded? or does it just load the one that’s in the folder for the child theme?

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    It loads both the child and parent theme’s functions.php, as noted above.

    Thread Starter joeborders

    (@joeborders)

    Yes, I know, what i mean is, we have the theme and child theme A and child theme B. is it possible that something has been mis-coded so that child theme A is loading child theme B’s functions.php?

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘Query string parameters being stripped and we don’t know why’ is closed to new replies.