WP Engineer » WordPress News

Custom Post Type and Permalink

Frank — Wed, 28 Jul 2010 13:37:05 +0000

Since WordPress 3.0 you can use Custom Post Types and you can define your own types of content - it's more like pages than posts! Thereby you can use automatically the Permalink structure of your WordPress installation. That means, if you create a new post type, you can use Permalinks.

But the Permalinks only work if you recreate the Rewrite Rules of WordPress - that's why many users initially have problems with it. If you create a new post type you probably get a 404 if you open this page because WordPress doesn't know the URL-structure in your Permalinks since you didn't create the Rewrite Rules again.

The easiest way is to safe the Permalink structure in your settings again. Alternatively you can include in your Plugin or Theme the function flush_rewrite_rules(). This enables to create the Rewrite Rules again.

Thanks for subscribing our feed! Sponsor the WP Engineer Blog and get your brand in front of several hundred users per day!
© WP Engineer Team, All rights reserved (Digital Fingerprint: WPEngineer-be0254ce2b4972feb4b9cb72034a092d)

WordPress Import Not Include In WP Core

Frank — Wed, 30 Jun 2010 09:30:34 +0000

WordPress came with several new or changed features - one feature which changed is the functionality to import content from other systems.

WordPress offers under "Tools" to import data of other applications or a XML-file of another WordPress installation. But since WordPress 3.0 you need a Plugin because it is no longer in WordPress core. The installation of the Plugin is easy and has the usual steps to activate a Plugin.

This is the first time, that WordPress is going into the direction of using Core-Plugins. There are many formats available if you check out the profile of WordPress, and maybe someone can create additional importers for other formats.

WordPress 3.0 Nav Menu UI Update

Michael — Tue, 27 Apr 2010 13:24:10 +0000

I just recognized, that the Nav Menu UI of WordPress 3.0 got updated. Here are 2 screenshots from the trunk:

WordPress Developer Hint

Frank — Tue, 27 Apr 2010 05:55:14 +0000

With WordPress 3.0 debugging will be easier, whereas one constants gets eliminated and an already existing constant will do their work.

For developers the following 3 constants are important and should exist in every wp-config.php of a development system. Please use it with precaution on a live system!

Add define('WP_DEBUG', true); to wp-config.php to enable
the reporting of notices during development.
Add define('WP_DEBUG_DISPLAY', false); to wp-config.php to
disable the display of errors.
Add define('WP_DEBUG_LOG', true); to wp-config.php to log
eerrors to debug.log in the wp-content directory.
Sets PHP error handling and handles WordPress debug mode.

Recommendation for wp-config.php

/** Debugging WP */
define('WP_DEBUG', true); //enable the reporting of notices during development - E_ALL
define('WP_DEBUG_DISPLAY', true); //use the globally configured setting for display_errors and not force errors to be displayed
define('WP_DEBUG_LOG', true); //error logging to wp-content/debug.log
define('SCRIPT_DEBUG', true); //loads the development (non-minified) versions of all scripts and CSS and disables compression and concatenation,
//define('E_DEPRECATED', true); //E_ALL & ~E_DEPRECATED & ~E_STRICT

A small syntax with huge impact. I recommend this to everyone who is developing with WordPress, especially with Xdebug a fantastic help.

Shortlinks with WordPress 3.0

Frank — Thu, 22 Apr 2010 05:52:10 +0000

There will be a new function in the coming 3.0 version, which will create a shortlink to a post. At default it will be in the header of your frontend.

A shortlink would always be with ?p= syntax and the ID of the post.

To use the shortlink in your theme, you can use a template tag with 4 parameters.

 * @param string $text Optional The link text or HTML to be displayed.  Defaults to 'This is the short link.'
 * @param string $title Optional The tooltip for the link.  Must be sanitized.  Defaults to the sanitized post title.
 * @param string $before Optional HTML to display before the link.
 * @param string $before Optional HTML to display after the link.
 */
the_shortlink($text = '', $title = '', $before = '', $after = '')

Here an example how you can use it in your theme:

if ( function_exists('the_shortlink') ) the_shortlink( __('Shortlink'), __('kurze URL zu diesem Beitrag nutzen'), ' · ' );

The function wp_get_shortlink() is in use in this case. You should use this function if you don't want to have it displayed (echo).

The link in the head of the frontend is created via a hook and can only get disabled. The integration will be standard in WordPress 3.0:

add_action( 'wp_head', 'wp_shortlink_wp_head', 10, 0 );

To deactivate the syntax in the head of your template you can put the following code in your functions.php.

remove_action( 'wp_head', 'wp_shortlink_wp_head', 10, 0 );

If you like to adjust the shortlink to your liking, you can use several filter hooks.
pre_get_shortlink // Allow plugins to short-circuit this function
get_shortlink // Filter the output

Better Plugin List in WordPress 3.0

Frank — Thu, 15 Apr 2010 17:29:48 +0000

One of the main reason why WordPress is so popular is the amount of available Plugins. Most users using Plugins via the most popular way - in the folder plugins under wp-content, and activate them in the backend of WordPress. For other possibilities of plugin integration WordPress 3.0 try to provide a more user friendly way.

WordPress offers many possibilities to hook into the system, sometime they are better and faster.

For this reason the admin can find a new tab on the Plugin page "Drop-ins", see screenshot below of the current beta 1.

In comparison a screenshot of WordPress 2.9.

There is also a tab for must-use plugins. Plugins can be stored in a "WordPress MU"-plugins folder.

WordPress 3.0 Menu Update

Michael — Tue, 16 Mar 2010 00:01:15 +0000

The new menus WordPress 3.0 just got an update, provided by Ptah Dunbar. Thanks Ptah, cool work! I checked out the new version. But first a screenshot of the backend:

As you can see, you can build your menu from modules. Right now these are pages, posts, custom links, categories, tags and media. You can sort the entries in your menu via drag & drop. Here an edit menu item screenshot:

New Screenshots Of WordPress 3.0

Michael — Fri, 26 Feb 2010 16:38:58 +0000

Unfortunately we don't have time right now to write new posts, but at least we want you to show some new screenshots of WordPress 3.0.

WordPress 3.0 Background settings

Now you have the option to set positon, repeat and attachment.

WordPress 3.0 Header Image

8 header images are available in the new theme TwentyTen.

WordPress 3.0 Menu Settings

First Impressions of Custom Post Type

Frank — Thu, 11 Feb 2010 07:07:36 +0000

One of the new very interesting things in WordPress 3.0 are individual post-types you can implement with little effort. Back then, you had to expand the database and write your own interface for it, now you just have to add a few lines of code - of course this is just the current state, which can be change until the final release.

After Justin had been playing with these types, we check out the possibilities of types for "Movies".

Simple Solution

function post_type_movies() {
	register_post_type( 'movies',
                array( 'label' => __('Movies'), 'public' => true, 'show_ui' => true ) );
	register_taxonomy_for_object_type('post_tag', 'movies');
}
add_action('init', 'post_type_movies');

More parameters for meta-boxes

Of course there are a number of parameters for this function and so the behavior and appearance of the corresponding edit page can be controlled quite easily, a small sample with additional meta boxes:

function post_type_movies() {
	register_post_type(
                     'movies', 
                     array('label' => __('Movies'), 
                             'public' => true, 
                             'show_ui' => true,
                             'supports' => array(
                                        'post-thumbnails',
                                        'excerpts',
                                        'trackbacks',
                                        'custom-fields',
                                        'comments',
                                        'revisions')
                                ) 
                      );
	register_taxonomy_for_object_type('post_tag', 'movies');
}
add_action('init', 'post_type_movies');

The default arguments

// Args prefixed with an underscore are reserved for internal use.
$defaults = array(
    'label' => false,
    'publicly_queryable' => null,
    'exclude_from_search' => null,
    '_builtin' => false,
    '_edit_link' => 'post.php?post=%d',
    'capability_type' => 'post',
    'hierarchical' => false,
    'public' => false,
    'rewrite' => true,
    'query_var' => true,
    'supports' => array(),
    'register_meta_box_cb' => null,
    'taxonomies' => array(),
    'show_ui' => null
);

label - A descriptive name for the post type marked for translation. Defaults to $post_type
public - Whether posts of this type should be shown in the admin UI. Defaults to false
exclude_from_search - Whether to exclude posts with this post type from search results. Defaults to true if the type is not public, false if the type is public
publicly_queryable - Whether post_type queries can be performed from the front page. Defaults to whatever public is set as
show_ui - Whether to generate a default UI for managing this post type. Defaults to true if the type is public, false if the type is not public
inherit_type - The post type from which to inherit the edit link and capability type. Defaults to none
capability_type - The post type to use for checking read, edit, and delete capabilities. Defaults to "post"
edit_cap - The capability that controls editing a particular object of this post type. Defaults to "edit_$capability_type" (edit_post)
edit_type_cap - The capability that controls editing objects of this post type as a class. Defaults to "edit_ . $capability_type . s" (edit_posts)
edit_others_cap - The capability that controls editing objects of this post type that are owned by other users. Defaults to "edit_others_ . $capability_type . s" (edit_others_posts)
edit_others_cap - The capability that controls publishing objects of this post type. Defaults to "publish_ . $capability_type . s" (publish_posts)
read_cap - The capability that controls reading a particular object of this post type. Defaults to "read_$capability_type" (read_post)
delete_cap - The capability that controls deleting a particular object of this post type. Defaults to "delete_$capability_type" (delete_post)
hierarchical - Whether the post type is hierarchical. Defaults to false
supports - An alias for calling add_post_type_support() directly. See add_post_type_support() for Documentation. Defaults to none
register_meta_box_cb - Provide a callback function that will be called when setting up the meta boxes for the edit form. Do remove_meta_box() and add_meta_box() calls in the callback
taxonomies - An array of taxonomy identifiers that will be registered for the post type. Default is no taxonomies. Taxonomies can be registered later with register_taxonomy() or register_taxonomy_for_object_type()

Including Custom Taxonomies

In the following example we include in our Post-Type a Taxonomy with two possibilities; own Tags and categories for Post-Type Movies, the classical tag, without hierarchy and one as category, tag with hierarchies.

function post_type_movies() {
	register_post_type(
                'movies', 
                array(
                        'label' => __('Movies'),
                        'public' => true,
                        'show_ui' => true,
                        'supports' => array(
                                     'post-thumbnails',
                                     'excerpts',
                                     'trackbacks',
                                     'custom-fields',
                                     'comments',
                                     'revisions')
                )
        );
 
	register_taxonomy( 'actor', 'movies', array( 'hierarchical' => true, 'label' => __('Actor') ) ); 
 
        register_taxonomy( 'production', 'movies',
		array(
                         'hierarchical' => false,
			 'label' => __('Production'),
			 'query_var' => 'production',
			 'rewrite' => array('slug' => 'production' )
		)
	);
}
add_action('init', 'post_type_movies');

Definitely a very interesting and useful feature which provides many possibilities to play around with.

WordPress 3.0 Custom Background Support

Michael — Wed, 10 Feb 2010 08:22:34 +0000

In WordPress 3.0, it will have, additional to the Custom Header Image support, also a Custom Background Support. A first snapshot is in the current trunk. To use the functionality, the theme needs in functions.php this line:

add_custom_background();

After that, there is in your backend under Appearance the menu Custom Background available.

After uploading an image, you have the option to activate "Tile the background" and delete the background image.

Here the result with the new Theme Twenty Ten.

WP Engineer » WordPress News

Custom Post Type and Permalink

Related posts:

WordPress Import Not Include In WP Core

Related posts:

WordPress 3.0 Nav Menu UI Update

Related posts:

WordPress Developer Hint

Related posts:

Shortlinks with WordPress 3.0

Better Plugin List in WordPress 3.0

Related posts:

WordPress 3.0 Menu Update

Related posts:

New Screenshots Of WordPress 3.0

WordPress 3.0 Background settings

WordPress 3.0 Header Image

WordPress 3.0 Menu Settings

Related posts:

First Impressions of Custom Post Type

Simple Solution

More parameters for meta-boxes

The default arguments

Including Custom Taxonomies

Related posts:

WordPress 3.0 Custom Background Support

Related posts: