Hi, I have 3 shipping options with different prices and prices do not update on the checkout page when switch between different shipping options. Once I deactivate a plugin everything works fine but with the plugin activated, once you choose one shipping option on cart page, the system does not register the change on checkout page and saves only the option chosen in cart. On checkout it looks like you can change the option because you check it and system seems like refreshing but prices do not update and when client finishes the checkpout, order comes in with the 1st chosen shipping option. Currently plugin is deactivated because it is annoying for clients, but maybe you have some solution to exclude checkout so I can continue using it?
]]>Wordfence is tagging this plugin as a critical issue saying “The Plugin “Remove Query Strings From Static Resources” has been removed from www.ads-software.com.
Type: Plugin Removed”
Could you clarify the state of the plugin and whether or not it’s safe to still use it?
Thank you for your time.
]]>Wordfence is describing a critical error with this plugin. This is due to the plug in being removed from WordPress. Could you please provide an explanation for this? Otherwise we will be removing it from our site and seek an alternative measure for this issue.
]]>The plugin which supposedly was approved for my theme has had absolutely no effect. I would appreciate some advice on what plugin that is effective. I have tried a couple and have not had any success. Thanks in advance.
https://www.oldeworldelace.com
I am checking all our plugins because with the last WordPress update (4.9) half of our plugins are not compatible, including yours. When will you be updating this plugin?
]]>As a plugin author, plugins that do this are a big cause of trouble.
You have an FAQ that says that this technique works for all websites. What you haven’t explained anywhere is that the consequences of removing the version string is that, after an update, resources may no longer work properly.
e.g. If the PHP of a plugin is closely tied to its JavaScript, and if a new version of that plugin changes both, then after an update they may get a new DOM setup in the browser, but receive old, cached JavaScript because of the versioning being removed by your plugin – resulting in website breakage. As a plugin developer, I’ve seen that plenty of times – it’s an annoying support burden. Please can you at least explain to your users that the plugin may cause breakage of their website.
]]>