Kimberly

Hi ya!

From looking at the code way back i notice this plugin requires you do one of two things:

1. Give the full path to the file. If its a directory then the full path to the directory, postfixed with a “*”. e.g. /home/hosting-username/blog/wp-content/uploads/wpcf7_captcha/*

OR

2. Add a “*” wildcard at the very beginning of each relative path. But if the path is for a directory you will also need to postfix another “*”. e.g. */wp-content/uploads/wpcf7_captcha/*

Notice the use of “*” wildcard at the beginning and end above. For directories you want to make sure to use the “*” at the very end. However, to ALSO use relative paths you would also need to use a “*” at the very beginning too.

This is why your first full path didn’t work — you didn’t include a “*” at the end. And the other two paths (relative) were missing “*” at the beginning.

So in summation either of the following would now work:

/home/hosting-username/blog/wp-content/uploads/wpcf7_captcha/*
*/wp-content/uploads/wpcf7_captcha/*

One thing u have to be careful though is wordpress and plugins 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 false positiving 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.

Unless i am misunderstanding you, you could just set this plugin (via its Options page) to use “Other Cron” from the “Cron Method” dropdown box.

That is what i’ve done. And from there i just add the recommended cron line to my cron list. Actually, i changed his recommendation to something else but it still works fine.

Some of us have been using a forked version of this which still works in v3.8.1 perfectly.

Use the following:

<!– WP-Minify JS –>
<!– WP-Minify CSS –>

yup we in the forums noticed that too a few years back and so several of us here made a forked version of wp-minify to implemented patches that resolved this and a few other problems.

there are ways to resolve it and id love to help but experience says it wont be long before my efforts to help will soon go ignored.