Kimberly

One thing u have to be careful though is plguins like to use special ids for their POST/REQUEST and so this could be picked up by Screamer and flag it as bad and potentially get your self banned from the Admin page (and entire site) accidentally. So u want to make sure when u enable the Ban feature to be aware that you may need to do some adjusting by including post/get ids in its Exception field.

For me, i kept getting confused why i kept getting locked out when i attempted to edit preferences for another plugin. Took me a while to notice it was screamer creating a false positive on my navigating/saving attempts in Admin page…yikes.

I was forced to go into the database, search for my ip to locate which tables it was in and remove the rows (with my ip) that were related to screamer and that fixed the problem. I also took note of the “REQUEST.xxx” and “POST.xxx” columns to include them into Screamer’s exception list. With that done it fixed the problem perfectly.

So this isnt a flaw of Screamer it is just being very sensitive to what is going on and it doesnt know who is an intruder or not — the maker of this plugin could have included a more detailed exception list that included not just the field name but values in the field since intruders could use the same fields but the data could be different; ip address exclusions would be nice too..

What is the problem exactly?

guess im too late to give my 2cents

For me WP MInify works for 3.8 but then i am using a customized version where i personally fixed its bugs back in wordpress 2.8 and ever since its been working for every subsequent version. I finally ugpraded to v3.8 only a few days ago and was happily suprrised WP Minify is still working perfectly. Yay for me!

Yup i noticed that problem too which is why i rewrote some of this plugins internal code.

I assume yyour html page has a cache time (or is a cached file made by a quick cache type plugin). When that time expires it should go making updates, triggering this plugin to reevaluate its minified .js file to a new name (if necessary).

I noticed internally his method for naming these files (md5) is a bit improper and under conditions can cause problems. I rewrote my forked version of this plugin to resolve most of his problems, and by extension my problems.

Unless i am misunderstanding couldnt you just have enable the Quick Cache option to cache Get queries? Since JSON queries include the “?” symbol (akin to Get queries) this would automatically cache each and every JSON query request individually.

However, you will run into problems if you don’t want it to cache all queries that include “?” and so you would have to use wildcard statements to exclude all queries you don’t want cached — another avail Quick Cache field.

1. Could be your Server overriding your cache control settings

2. You can set cache settings via PHP (via header() function calls) and/or through your .htaccess file