Custom post types is a very powerful feature in WordPress 3.0. With custom post types you can easily create post-like objects and automatically have menus, metaboxes, icons, permalinks, and much more added without having to code any of it yourself.
Here we consider custom post type permalinks – how to set it, what the different options mean, and how each of them affects your custom post type permalink structure.
In Custom Post Type Permalinks- Part 2, we consider how to flexibly modify the permalinks to something other than the given defaults. This article gives a more in-depth explanation of WordPress permalinks in general.
In the examples below, we assume our new custom post type is called gallery.
Register Post Type Permalink Options
Permalink behavior can be easily defined in our call to register_post_type. The options in register_post_type that relate to permalinks include -
Defines whether users can query our custom post type from the main blog page. For example, if we set publicly_queryable to true, we can enter -
This will show the gallery object that has the slug test-1. If publicly_queryable is set to false, then users will get a 404 or file not found error page instead.
Defines the name used in our public query above. query_var defaults to our custom post type name – e.g., gallery.
We can also set our query_var to be something else. For example, if we set the query_var argument to ‘foo’, then our gallery object query will look like this -
gallery=test-1 will no longer work because we have set our query_var to foo.
Rewrite will add pretty permalink rules for our new custom post type. For example, if we set rewrite to true, then we can access our gallery objects with the following link -
We can further specify two additional arguments in our rewrite argument –
'rewrite' => array('slug' => 'shiba-gallery', 'with_front' => FALSE)
This means our gallery pretty permalink will now become –
with_front determines whether or not to prepend our blog permalink structure in front of our custom post type object. If we set with_front to true and our blog permalink structure is –
Then both of the following permalinks will show our gallery object -
Permalink epmask is a bit more complex, and need not be used in most cases.
epmask stands for endpoint mask.
An endpoint is something that is added to the end of an object permalink. For example, /trackback/ is an endpoint.
Different endpoints are attached to different epmasks using the add_rewrite_endpoint command.
epmasks indicate which type of links an endpoint (e.g. /trackback/) should be added to. epmasks may contain the following values or combinations of the following values (for example if we want an endpoint to be added into several different types of links).
The permalink_epmask argument allows us to specify which group(s) of endpoints we want to add to our custom post type permalinks. For example, if we set permalink_epmask to EP_PAGES & EP_TAGS then we will associate all endpoints that are linked to pages and tags with our custom object permalinks.
The permalink_epmask argument defaults to EP_PERMALINK. This is the link type for regular posts. I.e., the same endpoints being added to posts will also get added to our new custom post type.
If we do not want to add any endpoints to our new gallery object, then we want to set permalink_epmask to EP_NONE.
If we want to add all endpoints to our new gallery object, then we want to set permalink_epmask to EP_ALL.
Flush Permalink Rules
Note – If you change permalink settings, you may need to flush your previous rewrite rules before the new changes will take effect.
To do this, you want to add the flush_rules function call to your plugin activation and deactivation function.
// add to your plugin deactivation function global $wp_rewrite; $wp_rewrite->flush_rules();
Custom Post Type Permalinks- Part 2 explains how we can fully modify our entire custom post type permalink structure.