jeffvls

Marking this ticket as resolved. It’s not an issue with the plug-in, but is based on how our theme/programming is set up.

OK, I figured out what was happening. The meta keys for all of the post-meta/custom fields were named with an underscore at the beginning of the meta key (for example
“_city” instead of “city”). This is a method of creating “hidden custom fields” that WP ignores them in the back-end.

Description:
If you are a plugin or theme developer and you are planning to use custom fields to store parameters related to your plugin or template, it is interesting to note that WordPress will not show custom fields which have keys starting with an “_” (underscore) in the custom fields list on the post edit screen or when using the the_meta() template function. This can be for example used to show these custom fields in an unusual way by using the add_meta_box() function. For more info, see here: https://codex.www.ads-software.com/Function_Reference/add_post_meta#Hidden_Custom_Fields

So my solution will be to look into seeing if its possible for us to rename our meta keys so that they are not using the underscore at the beginning.

Thanks for the great plug-in!

We just happened across this as well. It looks as if the second “status” key should be an “AND” instead? So it should read:

//Find unused urls
$query = "select id from " . $wpdb->prefix . "wbz404_redirects where status = " . $wpdb->escape(WBZ404_AUTO) . " and ";
$query .= "timestamp <= " . $wpdb->escape($then) . " and id not in (";