3.1 RC3: Uppercase custom post type problems

Thank you very much for the reply!

I am aware of the slug usage and I have left this setting to default, and as the documentation says:

‘slug’ – prepend posts with this slug – defaults to post type’s name – use array(‘slug’=>$slug) to customize permastruct

So I guess this means that the slug here is “Portfolio” (the same as the post type).

To be more clear, here is the code used for registering the custom post type:

register_post_type( 'Portfolio',
		array( 'labels' => $labels,
	         'public' => true,
	         'capability_type' => 'post',
	         'hierarchical' => false,
	         'supports' => array('title', 'editor', 'thumbnail', 'comments', 'page-attributes') ) );

I think that if I set the post type to be “Portfolio”, this should work everywhere I try to use it (and it did prior to 3.1 RC3).
For example, with version 3.0.4, in the “Add post” page when using:

$current_screen->id

it returned “Portfolio”, but with 3.1 RC3 it returns “portfolio”.

If I change now the slug to “portfolio”, there still will be lots of changes that I will have to do on the theme and even if I do it and release an update, I think people might experience some problems.

So far, what best works for me is to check if the post exists with the uppercase or lowercase, before referring to it:

if(post_type_exists(‘Portfolio’)){
$portfolio=’Portfolio’;
}else{
$portfolio=’portfolio’;
}

And the most interesting part is that on some places I still can use “Portfolio” (for example with the query_posts function) and on other using “Portfolio” just doesn’t work.

Thanks again

Actually, I understand it now, but obviously when creating the theme I got mislead by the default value for $post_type set to “None” in the function reference.

Changing this to a working site with existing Portfolio posts messes some parts, so I can’t do it now, but I will have to think of a way to do it compatible for both WordPress versions.

Anyway, thank you for your time, your help is much appreciated 🙂

Hi Ipstenu,

The problem is not with my own installation, but the installations of other people using the theme (they are not few). They already have set their sites with Portfolio posts created and some of their portfolio functionality will break with the new update, but I can’t tell them to update the database, as lots of them don’t have the knowledge to do it.

So I can’t neither register the portfolio post type with a lowercase slug, nor update the database. The only thing that is left for me now is to check whether the “Portfolio” post type exists (as posted above), and if not, to refer to it as “portfolio”.

Thank you very much for your help 🙂

Thanks for the idea – it seems that it will do what I need, I will give it a try 🙂

By the way, I have been thinking about adding a function that checks whether “Portfolio” posts exist and if yes, just creates a query to the database that updates all the “Portfolio” types to “portfolio”. After that I should be able to refer to the posts as “portfolio”.

Thanks again 🙂