Hi Emre,
I’m the author of WP-SpamShield. Feel free to contact me directly (you can use the contact form on my site if you like) to help bridge any gaps between our plugins.
I think what you said about removing the query string if the extension is php is a good one.
The script you mentioned above shouldn’t have a query string added to it, because that will keep it from working. That’s why I didn’t enqueue it, to prevent issues. I’d recommend….just my opinion here…that if you’re going to combine and minify JS and CSS that you only do it to ones that are in the WordPress queue. Also, I’d recommend not adding any new query strings to scripts. WordPress already does that but only to the scripts in the queue, which is in my opinion, the best way to handle it. Also, some people like to remove these via a plugin, and it would seem that this implementation would interfere.
“Removing query strings from static resources” is also one of Google PageSpeed’s metrics because it benefits caching on the browser side (query strings prevent a JS or CSS file from caching in a browser, thus requiring a fresh load of the file on every page load, which slows down the works), so removing them will help improve the PageSpeed results from your plugin. I understand if you have reasons for having them…just thought I’d offer that too.
Keep up the great work on WP Fastest Cache. I’ve heard good things. ??
– Scott
