Paul Menard

I’m the plugin author for Simply Exclude. The plugin makes not code changes to you core code, other plugins or your theme. The plugin works purely on hooks which are executed when the page is request. These hooks effect the queries use by WordPress when displaying the categories, tags authors, pages.

If you didn’t like the plugin then please just deactivate it. This will disable all interactions with the WordPress hooks. Nothing is left to do except remove the plugin from your system.

If you are still having issues please feel free to contact me directly.

kperrone, thanks for your response on this.

Best,

P-

dimadin, Thanks for posting this and digging through an answer. I’m also working to add a field to the Permalinks admin page for my Media-Tags plugin. Though currently this is an issue I found a work around that I wanted to share.

You are (or should be) setting an action for ‘admin_init’ to call your function. Inside this function you are then calling ‘add_settings_field’ or ‘register_settings’, etc. In my code I’m checking if the $_POST variable I set via my input field is available. If so and if the referrer URL is options-permalink.php then I just update the options myself.

Hey there. I’m the plugin author for Simply Exclude. Not sure I can understand how the exclusion of categories,tags can effect the actual shortcode which is content level information. But will look into it. If this the WordPress provided [gallery] shortcode or from a specific plugin??

Sorry for the delay on the update dblast. I had not update the WP 2.7 hash config for the latest file changes. I just post a new updated version 1.2.1 into the www.ads-software.com SVN repository. Give it a few minutes then check your WordPress plugin for the update.

This should now be fixed in version 1.6 of the Simply Exclude plugin. Just uploaded to SVN this evening. Along with some other changed for handling searches within the admin. Some cosmetic cleanup to make the plugins pages look more WP 2.5-ish.

So I guess this was NOT fixed in 2.5.1?

Well according to the page heirarchy https://codex.www.ads-software.com/Template_Hierarchy home.php is still used if present. I’ve tested this. If I don’t set an option on the Reading section then the home.php is used.

My problem is I *need* to set the home page (/) to have certain page content. So my assumption was using the Reading options would provide the solution.

I’d like to throw in my solutions. It simple and less code.

In your theme folder create a functions.php is one does not exist. In that file place the following:

function myBlogPostsFilter($query)
{
global $wp_query;

// I just want to work with searches not all global queries.
if ($query->is_search)
{
// The line below sets/unsets the categories to search
// To exclude a category just provide the cat_id with
// a preceeding ‘-‘.
$query->set(‘cat’,’-3,-4,-5,-6,-7′);
}
return $query;
}
add_filter(‘pre_get_posts’,’myBlogPostsFilter’);

Thanks. Yeah I’ve not looking into flushing the cache on the admin screen. Maybe something for the next version.

Thanks David. Yeah the whole issue brought up a small discussion over the new WP cahce system. Seems of the three developers on the room we each had our own opinions of what this does.

I do think there are some setup issues still with from the Akamai end. This is one complicated system.

Thanks again.

Well I meant Pages as in WP Pages (not Posts). When I converted the client site they have these static folders ‘CM’, ‘Lword’ and ‘FR’ sub-folders that contained single index.php files in each.

I of course wanted to use as much WP functionality as I can. So I enabled permalinks. So that instead of the links showing as https://www.some_domain.com/?p=123 or whatever I wanted ‘pretty’ URLs like https://www.some_domain.com/lword.

The issues is the uppercase URL versions of ‘CM’, ‘Lword’ and ‘FR’ are out there in the search engine cache and also on job posting site (The CM and FR folders are for jobs). The client insisted they still work.

As I mentioned I setup a redirect in Apache to handle this. I could solve the issue for the other two URLS in the same manor.

But I was thinking, what if the client creates new pages (lowercase page slugs) but some web surfer enters uppercase for the URL. The page is not reached. They must be lowercase. This is where my interest in a mod_rewrite rules stems.

I’m guessing there is also a way to have Apache ignore case via some httpd.conf setting.

Sure I’ll try anything. Though I was hoping for something that does not depend on the user selecting something when creating a post. Thanks.

By the way. If anyone sees this post please reply. I don’t want to close this issue just yet.