Ron Strilaeff

bravenewniche… I’m glad my experimentation has helped you.

Well, I just checked again and my oldest stale cache files were from 2 months ago, the file count was 32k and the disk space used was 3.9GB.

Changing the cache expiration time (from 3601 back to 3600 this time) did remove all the files within a minute or two without ever disabling the cache. So that’s a nice workaround, but not a fix.

It seems that this plugin must be ignoring that config value, except when it is changed. OR… maybe it is working making new cache files without deleting the stale ones. The description of that setting (in the plugin) doesn’t say anything about actually removing old files.

Other than having to do this housekeeping, the plugin has been solid: it seems to do its job efficiently, and stay out of the way.

Hey I don’t have time to track this down myself, but I was just checking some log and config files on my server and stumbled on this error when I was playing with your plugin.

Apparently it is not hard to create a situation in which the “WHERE” clause is empty:

[Mon Apr 08 18:29:22 2013] [warn] [client 174.66.18.85] mod_fcgid: stderr: WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND ff_posts.post_status = 'publish'' at line 5 for query , referer: http://strilaeff.net/blog/replacing-motor-mounts-on-a-vw-passat/
[Mon Apr 08 18:29:22 2013] [warn] [client 174.66.18.85] mod_fcgid: stderr: \t\t\tSELECT *,, referer: http://strilaeff.net/blog/replacing-motor-mounts-on-a-vw-passat/
[Mon Apr 08 18:29:22 2013] [warn] [client 174.66.18.85] mod_fcgid: stderr: \t\t\tsubstring(post_content, 1,200), referer: http://strilaeff.net/blog/replacing-motor-mounts-on-a-vw-passat/
[Mon Apr 08 18:29:22 2013] [warn] [client 174.66.18.85] mod_fcgid: stderr: \t\t\tAS excerpt, referer: http://strilaeff.net/blog/replacing-motor-mounts-on-a-vw-passat/
[Mon Apr 08 18:29:22 2013] [warn] [client 174.66.18.85] mod_fcgid: stderr: \t\t\tFROM ff_posts WHERE , referer: http://strilaeff.net/blog/replacing-motor-mounts-on-a-vw-passat/
[Mon Apr 08 18:29:22 2013] [warn] [client 174.66.18.85] mod_fcgid: stderr: \t\t\tAND ff_posts.post_status = 'publish' made by do_action('wp_ajax_nopriv_wpus_search'), call_user_func_array, WPUltimateSearch->get_results, WPUltimateSearch->execute_query_basic, referer: http://strilaeff.net/blog/replacing-motor-mounts-on-a-vw-passat/

glhf

Thanks for looking at it, maybe I can help you by being a typical test site. I don’t need it to work yet, since our live site (where I would like some ajaxified advanced search) will not be ready for a month or two. Even then I will probably just have some category drop downs to start.

Anyways, here is the content of my /search (or /search/) page:

content before shortcode [wp-ultimate-search-results] content after shortcode

In firefox, on my site, the shortcode produces no content. There is one space on either side of the square brackets.

I just tested it as network activate vs subsite activate and it behaves the same so I will leave it as subsite activate.

(Forget chrome for now, the search widget it is just unresponsive there and i’m pretty sure the google search js stuff in a text widget at the top of my sidebar is not interfering.)

Good to know, thanks!

So to remove the messages like this on my options/admin pages:

echo "<div id='message' class='updated fade'><p><strong>Options Saved</strong></p></div>";

I enqueued a little js file which includes this jQuery snippet:

jQuery(document).ready(function($){ // doc ready wrapper.  the '$' means I can use '$' instead of 'jQuery' within this scope.

$('.fade').click(function(){$(this).fadeOut('fast');}); 

}); // end of doc ready wrapper

IMHO it is better to remove the message after acknowledging it with a click instead of just an auto fadeOut. But from a UI point of view, it really should go away after *any* change is made to the page.

Thanks again … resolved!