But you can solve the problem with a Hook in the registry of your Framework/Basic-Theme.

//Code of the Framework to register 2 Sidebars
function xtreme_register_dynamic_sidebars() {
  register_sidebar( array(
    'name' => 'Sidebar One',
    'id' => 'sidebar-one',
    'description' => 'Sidebar One',
    'before_widget' => '<li id="%1$s" class="widget %2$s">',
    'after_widget' => '</li>',
    'before_title' => '<h5 class="widget-title">',
    'after_title' => '</h5>'
    ));
  register_sidebar( array(
    'name' => 'Sidebar Two',
    'id' => 'sidebar-two',
    'description' => 'Sidebar Two',
    'before_widget' => '  <li id="%1$s" class="widget %2$s">',
    'after_widget' => '</li>',
    'before_title' => '<h5 class="widget-title">',
    'after_title' => '</h5>'
    ));
  do_action('childtheme_sidebars');
}
add_action( 'widgets_init', 'xtreme_register_dynamic_sidebars' );

You see the Hook do_action('childtheme_sidebars');
let's use this Hook:

//functions.php im Child-Theme
function xtreme_unregister_sidebar() {
    unregister_sidebar('sidebar-two');
}
add_action( 'childtheme_sidebars', 'xtreme_unregister_sidebar' );

And the Sidebar is removed. Easy huh?

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)

Sorry to all our readers and advertising partner for any inconvenience and we hope we won't have any problems like this in the future. So we will have more time to write more in depth tutorials, hacks or tricks about WordPress!

Thanks a lot!

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)

User Rights

A simple solution is to query the rights of the user - the WordPress function current_user_can() makes it possible and it is simple to implement in your theme template. Therefore you can control that only logged in user are able to access the content.
Simple example how to implement it in a template:

if ( current_user_can( 'manage_options' ) )
	the_content( the_title( '', '', false ) . ' ' . __( 'read  more»', FB_BASIS_TEXTDOMAIN ) );
else
	_e( 'Only for logged in users', FB_BASIS_TEXTDOMAIN );

There are many solutions which are considering the different roles and objects. You can find a nice overview of objects per role at Codex.

Proof of Login via Function

Now the integration in the template is quite simple, but you normally have to adjust every template. Since WordPress uses hooks, you can also hook into and via Plugin or functions.php put a function in your template.

The following function is as an example and examines regardless of the user rights only if the user is logged in - if so, content may be seen. With the help of the hook the_content it controls it - so that the output in the theme, which comes via the template tag the_content() is only visible if you are logged in as a user.
Also explicitly in your feed, the output is only visible when you are logged in - !is_feed().

As an alternative for non logged users a section of the content is displayed - there are different approaches, here it was done explicitly with characters. It creates kind of a teaser for the reader.

function content_only4logged_in($content) {

	// all logged in User
	if ( is_user_logged_in() &&
			!is_null($content) &&
			!is_feed()
		 ) {

		return $content;
	} else {

		$content  = wp_html_excerpt( $content, 80 );
		$content .= ' …';
		$content .= __( '<br />Sorry, more of this content is only available for logged users.', FB_TEXTDOMAIN );
		return $content;
	}
}
add_action( 'the_content', 'content_only4logged_in' );

Restrict Content via ShortCode

Another alternative is to make accessible only a certain section of the content only for logged in users. This could be done for example through the shortcode API of WordPress. In our example we use the shortcode [member] . Everything within this element is visible only to logged in users.
Also, this code belongs in a Plugin or in the interface of the themes for new features.

function fb_check_logged_in( $atts, $content = null ) {
	if ( is_user_logged_in() &&
		!is_null($content) &&
		!is_feed()
		 ) {

		return $content;
	} else {

		return __( 'Sorry, this content is only available for logged users.', FB_TEXTDOMAIN );
	}
}
add_shortcode( 'member', 'fb_check_logged_in' );

Time-dependent output

A possible alternative is to output a content for a specific period. This possibility can be safely extended to any size. So it's worth to use a Metabox to enter a date on the articles to query the time frame in a shortcode.

function content_only4time($content) {

	$date = strtotime( '01-10-2010' ); // day-month-year
	$now  = strtotime( date('d-m-Y') );
	echo $now . ' - ' . $date;
	if ( $date && ( $date < $now ) ) {

		return $content;
	} else {

		return __( '<br />Sorry, the time is not ripe.', FB_TEXTDOMAIN );
	}
}
add_action( 'the_content', 'content_only4time' );

In this case you can use the Plugin wpSleep , which controls via shortcode and parameters the time frame of the output.

More

The list of approaches and possibilities are endless. With the possibilities you may have your own ideas and can use the above mentioned examples. You are welcome to comment for further ideas and possibilities.

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)

The function of the Child Themes can be applied basically in every theme and the new features facilitate access and creation of a Child Themes. Before there were also possibilities to change a Theme without changing the actual files of the theme. With the support of Child Themes this is now completely independent and we can use a theme that can be updated without a problem, and you can still realize your own ideas.

Other blogs already mentioned Child Themes but I've found so far only posts where they just talking about the activation and modification of the style sheet. Therefore, I would like to comment this subject only briefly, which is quite simple and then show the different possibilities in terms of template files.

Advantages of Child Theme

More or less every administrator is trying to create an individual design for his WordPress system. This does not require to create a special theme from scratch. Very often, a free or commercial Theme is used and then adapted to your needs. Many Themes have different options but are not sufficient for customizing. If you want to adjust the individual design, such as the layout of a category, that requires some changes of the theme. No matter how extensive, an update of a Theme is no longer feasible without problems. Here the Child Themes come into consideration.

With a Child Theme, a Theme can be adjusted or you can use a Theme as a "Framework" and implement completely your own ideas. No matter how extensive, the real Theme remains intact and can undergo an update.

Disadvantages of Child Theme

Often "Framework" Themes are very comprehensive and with many features, sometimes it has a steep learning curve and customizing can cost a lot of effort and time. Even though with Child Themes.
A major disadvantage is also the performance, because WordPress have to look into two areas according to the template and get the according files.
Furthermore style sheets, if you build on them, are usually implemented via @-rule, which has disadvantages in performance.

In all the negative points, it depends on skill and knowledge of the developer and how the Theme or Child Theme is created. Thus you can weaken the negative arguments I pointed out. Important: The new function should be carefully considered before using it. But with Child Themes you don't have to touch the basic Theme and yet you can make adjustments easily.

Create Child Theme

Enough said, let's start with the example based on the Theme TwentyTen and create an adjusted Theme - I will call it TwentyTenJump

In the first step, a new folder is created in which we put all the template files, images, scripts and style sheets - what is principally needed for the Child Theme. In this example, the folder is twentytenjump. To create a Child Theme and make this apparent to WordPress, you simply need style.css within the new folder with several strings in a comment.

Within style.css it looks like this.

@charset "UTF-8";

/**
 * Theme Name:     TwentyTenJump
 * Theme URI:      http://bueltge.de/?p=1192
 * Description:    Child theme for the Twenty Ten theme. Realized for a small tutorial to child themes in WordPress.
 * Author:         Frank Bültge
 * Author URI:     http://bueltge.de/
 * Template:       twentyten
 * Version:        0.1.0
 */

@import url('../twentyten/style.css');

Important are the key Theme Name and Template. The key Template points to the folder name of the Theme, which is considered as a basis - in that instance, the Theme Twentyten.

I now have the following structure within the installation of WordPress.

• wp-content
  • themes
    • twentyten

    (Basic Theme, including all template files)

    • style.css
    • index.php
    • ...
    • twentytenjump
      • style.css (must satisfy these name convention: style.css)

Thus, the first requirements are in place and you can select the new Theme in the backend of WordPress.
Note: the reference to the Basic Theme is not very conspicuous, so that you might forget the dependency. So that's why you should always check before you delete a Theme. On the used Theme, there is no indication that a different Theme as a Child Theme is using this Theme.

Working on the style sheet

From now you can put any changes in your style sheet. Also, of course, you can remove the call to the style sheet @import url('../twentyten/style.css'); from the Basic Theme and you can build your own style sheet completely.

You use the template files, the structure and PHP know-how of the Basic Theme, in which case is Twenty Ten. You deal exclusively with the design. For example, this could be the simplest case, a change in color of the background and alternatively a completely separate design will be created.

Replace templates

The functionality of the Child Theme includes more than just changing the appearance. You can replace existing template files of the Basic Themes. WordPress looks first in the Child Theme and then in the Basic Theme for possible templates. WordPress runs through the hierarchy of template files.

At many points in your Theme you can intervene via Hook, which might be not very easy and complicated for some users. Thus not infrequently the output of title in head of a web site will be replaced with own functions or Plugins. You can either edit the title via Hook or control the output of a function. For example, the title should now be displayed with a function of a Plugin. In that case you have to adjust the header.php and so you must proceed as follows, so that the Basic Theme remains intact.

You only have to copy header.php, which is containing the head section of the Theme, into your own Child Theme and here it can be edited as you like. From now on WordPress pulls header.php and not the original file from the basic theme Twenty Ten.

Now you can integrate the mentioned function into the title, an example:

<title><?php
    /*
     * Print the <title> tag based on what is being viewed.
     * We filter the output of wp_title() a bit -- see
     * twentyten_filter_wp_title() in functions.php.
     */
    if ( function_exists('seo_title_tag') )
        seo_title_tag();
    else
        wp_title( '|', true, 'right' );

    ?></title>

The Basic Theme remains untouched, it can still be kept up to date via updates and from now on WordPress uses the header.php always of the Child Theme.

Like this small example you can replace any template and adapt to your own requirements. Nevertheless, you should bear in mind that you replace the template completely - in the example, we would not notice an update of header.php. So it may be helpful to use Hooks in various areas and have their own functions, more about this later.

Important: an exception is functions.php, I will talk more about it later.

Expand Templates

In order to meet your own requirements, it may be that you need new templates, template files didn't exist in the Basic Theme. For the purposes of the hierarchy you can extended forever. For example, Twenty Ten does not have home.php - you can simply place this file in your Child Theme and WordPress will use this file, if the state is_home() is true.

Using WordPress 3.0 there is another option outside of the template hierarchy to use your own templates - get_template_part().

This function is used consistently within Twenty Ten - so you don't have to create own templates for the complete call, but only for the section of the Loop.
For example, Twenty Ten uses for displaying the category archives the call get_template_part( 'loop', 'category' );. Thus it is possible to put a template in our Child Theme, which uses this loop. So it's only necessary to create a file loop-category.php and then save all necessary informations.

In the following example, I adjust the loop, if you are in one of the four categories. Other changes are possible, so you will have full control and flexibility.

if ( in_category( array(47, 37, 27, 45) ) ) {
	query_posts( 'cat='.$cat.'&posts_per_page=-1&orderby=title&order=ASC' );
}	else {
	query_posts( 'cat='.$cat.'&posts_per_page=20&paged='.$paged );
}
while ( have_posts() ) : the_post(); ?>

Similarly, you might be able to customize the loop for index.php - Template file loop-index.php would be in the game.

Include Functions

Of course you can also bring in the Child Theme your own functions. If you put an own functions.php in your Child Theme, then it does not replace the functions.php of the Basic Theme!
The functions of the Basic Theme will always be used. You have to disable them via the Hook. The possibility is also explained in a documentation in the functions.php file.

add_action( 'after_setup_theme', 'my_child_theme_setup' );
function my_child_theme_setup() {
		// We are providing our own filter for excerpt_length (or using the unfiltered value)
		remove_filter( 'excerpt_length', 'twentyten_excerpt_length' );
		...
}

Within the function my_child_theme_setup() you can disable the functions of the Basic Theme and bring in your own functions.

Other features belong into the functions.php of the Child Theme - the Basic Theme always remains untouched. In the following code example I disable the function of the Basic Theme Twenty Ten for the length of the excerpt, and load my own function twentytenjump_excerpt_length() and it includes a Widget.

<?php
function twentytenjump_setup() {

	remove_filter( 'excerpt_length', 'twentyten_excerpt_length' );
	add_filter( 'excerpt_length', 'twentytenjump_excerpt_length' );

	add_action( 'widgets_init', 'register_limited_catagories_widget' );
}
add_action( 'after_setup_theme', 'twentytenjump_setup' );

function twentytenjump_excerpt_length( $length ) {
	return 10;
}

class limited_catagories_list_widget extends WP_Widget {

	function limited_catagories_list_widget(){
		$widget_ops = array( 'classname' => __('Selective categories'), 'description' => __('Show a list of Categories, with the ability to exclude categories') );

		$control_ops = array( 'id_base' => 'some-cats-widget' );
		$this->WP_Widget( 'some-cats-widget', __('Selective Catagories'), $widget_ops, $control_ops );
	}

	function form ( $instance){
		$defaults = array( 'title' => __('Catagories'), 'cats' => '', 'count' => 0 );
		$instance = wp_parse_args( (array) $instance, $defaults );
		$count = isset($instance['count']) ? (bool) $instance['count'] :false;
		?>
		<p>
			<label for="<?php echo $this->get_field_id( 'title' ); ?>"><?php _e( 'Title:' ); ?></label>
			<input id="<?php echo $this->get_field_id( 'title' ); ?>" name="<?php echo $this->get_field_name( 'title' ); ?>" value="<?php echo $instance['title']; ?>" class="widefat" />
		</p>
		<p>
			<input type="checkbox" class="checkbox" id="<?php echo $this->get_field_id('count'); ?>" name="<?php echo $this->get_field_name('count'); ?>"<?php checked( $count ); ?> />
			<label for="<?php echo $this->get_field_id('count'); ?>"><?php _e( 'Show post counts' ); ?></label><br />
		</p>
		<p>
			<label for="<?php echo $this->get_field_id( 'cats' ); ?>"><?php _e( 'Categories to exclude (comma separated list of Category-IDs): ' ); ?></label>
			<input id="<?php echo $this->get_field_id( 'cats' ); ?>" name="<?php echo $this->get_field_name( 'cats' ); ?>" value="<?php echo $instance['cats']; ?>" class="widefat" />
		</p>
		<?php
	}

	function update($new_instance, $old_instance) {
			$instance = $old_instance;
			$instance['title'] = strip_tags( $new_instance['title'] );
			$instance['count'] = !empty($new_instance['count']) ? 1 : 0;
			$instance['cats']  = strip_tags( $new_instance['cats'] );
			return $instance;
	}

	function widget($args, $instance){
		extract( $args );
		$title = apply_filters('widget_title', $instance['title'] );
		$c     = $instance['count'] ? '1' : '0';
		$cats  = $instance['cats'];
		echo $before_widget;
		if ( $title )
			echo $before_title . $title . $after_title;
		echo '<ul>';
		wp_list_categories("exclude=$cats&title_li=&show_count=$c");
		echo '</ul>';
		echo $after_widget;
	}

}

function register_limited_catagories_widget(){
	register_widget('limited_catagories_list_widget');
}
?>

Conclusion

I think through the introduction of the new default theme Twenty Ten that some new cool features were added. But I think also that Twenty Ten is very inappropriate to understand the work of WordPress in the area of themes. Especially beginners and PHP newcomers are having a hard time. Yet it creates new opportunities and if you want to use Child Themes in a clean way, then you can not get around it without understanding Hooks in the WordPress API. WordPress takes the idea of the Hooks consistently further, always popular in Plugins, they do get popular in Themes now. Everything has advantages and disadvantages.

But if you use a well-maintained Theme or Framework, then you will appreciate the new possibilities and can always update with no problems. Crucial will be your own knowledge about WordPress - depending on the interest, knowledge and working methods how you create your own themes.

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)

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. Important: Flush rules only on activation or deactivation. Don't do it on any other hook.

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)

Alternatively, you can work with the ID of the page or article, function the_ID() passes it. Please note, IDs and classes may not start with a number and therefore you must add a string before, for example:

<div id="page-<?php the_ID(); ?>">

As a final alternative, I would like to mention that you can expand the function body_class() via Hook with own classes. So you can have the title of a page/post via hook in this function.

function fb_title_body_class($classes) {
	global $post;

	$classes[] = sanitize_title_with_dashes( get_the_title( $post->ID ) );

	return $classes;
}
add_filter( 'body_class', 'fb_title_body_class' );

In the following I'm showing you the simplest case via title, so that you output only this class and and body_class() is not used.

With the help of the Title

Put the stylesheet in the header of your Theme:

<link rel="stylesheet" href="<?php bloginfo('template_url'); ?>/custom.css" type="text/css" media="screen" />

Alternatively, this is integrated via Hook wp_head if the specific page is loaded, so you load the explicit style sheet only if it is needed. Everything happens in the functions.php of your Theme.

in your body tag of page.php is the title of the page:

<body class="<?php echo sanitize_title_with_dashes( get_the_title() ); ?>">

Therefore the page "My Home" has the body tag:

<body class="my-home">
and so on...

in your custom.css you define all style for class home: for example

.my-home a { color: #090; text-decoration: none; }
.my-home a:visited { color: #999; text-decoration: none; }
.my-home a:hover { color: #f60; text-decoration: none; }

in the original Theme it looks like this:

a { color: #009; text-decoration: underline; }
a:visited { color: #999; text-decoration: underline; }
a:hover { color: #c00; text-decoration: underline; }

I think it's an approach with a lot potential and so I leave it to your creativity. So if you would like to have for each page a different style sheet, this is an easy solution.

Alternativ a small plugin to add the title of the post to the template tag body_class() as example.

<?php
/**
 * Plugin Name: Title 2 body_class
 * Plugin URI: http://bueltge.de/wordpress-theme-in-abhaengigkeit-des-titel/397/
 * Text Domain: title2bodyclass
 * Domain Path: /languages
 * Description: Add the title of the post to the boy_class-function
 * Author: Frank Bültge
 * Version: 0.1
 * Author URI: http://bueltge.de/
 * Donate URI: http://bueltge.de/wunschliste/
 * License: GPL
 * Last change: 26.07.2010 10:37:23
 */ 

/**
License:
==============================================================================
Copyright 2010 Frank Bueltge  (email : frank@bueltge.de)

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

Requirements:
==============================================================================
This plugin requires WordPress >= 2.8 and tested with PHP Interpreter >= 5.2.9
*/

if ( !class_exists('title2body_class') ) {

    global $wp_version;
    if ( !function_exists ('add_action') || version_compare($wp_version, "2.8alpha", "<") ) {
        if (function_exists ('add_action'))
            $exit_msg = 'The plugin requires WordPress 2.8 or newer. <a href="http://codex.wordpress.org/Upgrading_WordPress">Please update WordPress</a> or delete the plugin.';
        else
            $exit_msg = '';
        header('Status: 403 Forbidden');
        header('HTTP/1.1 403 Forbidden');
        exit($exit_msg);
    }

    class title2body_class{

        define( 'FB_T2BC_BASEDIR', dirname( plugin_basename(__FILE__) ) );
        define( 'FB_T2BC_TEXTDOMAIN', 'title2bodyclass' );

        function __construct() {

            add_action( 'body_class', array( &$this, 'title_body_class' ) );
        }

        function title_body_class($classes) {
            global $post;

            $classes[] = sanitize_title_with_dashes( get_the_title( $post->ID ) );

            return $classes;
        }

        }
    }

    function title2body_class_start(){
        new title2body_class();
    }

    add_action('plugins_loaded', 'title2body_class_start');
}
?>

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)

But from time to time you need something specific, so I have some code snippets for you in this post now. And I particularly want to show some examples with jQuery. Many Themes and Plugins using jQuery and it is pretty easy to work with jQuery. In principle, these hooks and calls also apply to your own scripts and other libraries.

The Hooks

WordPress provides Hooks to hook at certain points into the core. This is one of the strengths of WordPress and the following three Hooks are in particular interesting to include scripts in your Themes. The following examples illustrate some practical use.

• init
• template_redirect
• after_setup_theme since WordPress 3.0

Replace jQuery of WordPress in your Theme with Google AJAX Library

In the following code the jQuery-Library of Google CDN gets loaded; But you can still use jQuery without any problem. Other Plugins can access the library very easy via wp_enqueue_script().

function fb_greyfoto_init() {
	if ( !is_admin() ) { // actually not necessary, because the Hook only get used in the Theme
		wp_deregister_script( 'jquery' ); // unregistered key jQuery
		wp_register_script( 'jquery', 'http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js', false, '1.4.2'); // register key jQuery with URL of Google CDN
		wp_enqueue_script( 'jquery' ); // include jQuery
	}
}
// nur for Themes since WordPress 3.0
add_action( 'after_setup_theme', 'fb_greyfoto_init' ); // Theme active, include function

jQuery Library in footer

The default call of wp_enqueue_script( 'jquery' ) in your Theme takes care, that it uses jQuery of WordPress and if all Plugins and Themes are setup correctly, the library will be load only once. But jQuery won't get loaded in your footer, instead in head of your site. That's why you have to adjust the code a little bit and add the parameter for "load in footer".
Here are two examples before and after WordPress 3.0 because after_setup_theme is only available since WordPress 3.0.

function fb_greyfoto_init() {
	if ( !is_admin() ) {
		wp_deregister_script( 'jquery' );
		wp_register_script( 'jquery', 'http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js', false, '1.4.2', true ); // load in footer - true
		wp_enqueue_script( 'jquery' );

		// load js of Theme, requires jQuery
		wp_enqueue_script( 'styleswitcher', get_bloginfo( 'template_directory') . '/js/styleswitcher.jquery.php', array( 'jquery'), '1.3.2', true ); // load my script with key styleswitcher in footer and use jQuery
		wp_enqueue_script( 'greyfoto', get_template_directory_uri() . '/js/photoblogfb.js', array( 'jquery', 'styleswitcher'), '1.1.3.1', true ); // use jQuery and styleswitcher and then load script greyfoto
	}
}

// also for WP < version 3.0
global $wp_version;
if ( version_compare($wp_version, "3.0alpha", "<") ) {
	add_action( 'init', 'fb_greyfoto_init' );
} else {
	add_action( 'after_setup_theme', 'fb_greyfoto_init' );
}

Load script for specific page

Sometimes you need some scripts just for a specific template, page or post - Therefore are Conditional Tags. This possibility improves the performance of your website. The following script will be loaded only for the template custom-page.php.

function fb_greyfoto_page_init() {
	if ( !is_page_template( 'custom-page.php' ) )
		return;

	wp_enqueue_script( 'mypagescript', get_template_directory_uri() . '/js/my_script_4_page.js', array('jquery'), '0.1', true );
}
add_action( 'template_redirect', 'fb_greyfoto_page_init' );

The usage of $

Within scripts you have to consider several things.
To work with $ , as many are used to with jQuery, you have to deliver jQuery to $ ; That's an easy task, the short version is $(function() {} ); , which should be used within WordPress.

jQuery(function ($) {
	// Now you can use $ as a reference to jQuery without any problem
});

To check whether the HTML is loaded, use the following call. That makes sure that the DOM is loaded and you can browse the DOM via jQuery and now the real work of the script can start. I strongly recommend to use this variant. I don't want to explain all the benefits, but you can read about it in the article Introducing $(document).ready().

jQuery(document).ready(function ($) {
	$('#id').toggle({
		//parameter for example toggle
	});
});

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)

Hope to see you there and if not, we probably will let you know what happened at the WordCamp Germany 2010 next week.

We also like to take the opportunity to say thank you to our loyal sponsors and like to introduce them to our readers, if you don't know them already:

If you also want to have a great design for your website, just get a PageLines Theme. They have superior themes for WordPress that make it simple for you to have an awesome, fully-featured website that is easy to set up and manage.

wpSEO is a great Plugin for better SEO on your WordPress installation. Check it out and you will love it as Google will love your blog from now on. Of course we are using it on WP Engineer too. WP 3.0 ready and with over 70 setting to optimize your blog. Join their affiliate program to participate on the success of wpSEO.

ThemeShift provides one of the most beautiful, powerful and state of the art WordPress Themes available these days. Take a look at them!

WishList Member is a powerful membership script that can turn any WordPress blog into a full blown membership site. Very interesting, you have to check it out. WishList Member belongs to our loyal sponsors, we are very glad to have them and to provide our readers a great membership plugin.

MakeBetterWebsites is a great gallery with a fine selection of high quality websites. All websites are handpicked and most of them I have first seen on this website instead of the usual suspects, seen on many other websites over and over again. Only high quality websites are seen on this website.

Download this book to become a Pro in WordPress! 400 Pages of Practical Information. A Lifetime Subscription, when you buy this book, you will instantly get the most current version. But also, you are getting a lifetime subscription to all updated (PDF) copies of the book. And lots of Code Samples!

Viva Themes creates quality and professionally designed WordPress themes. They offer themes for your business, blog or personal sites. All of that comes with an excellent free support

Tokokoo claims that they are offering the simplest way to build your online store with WordPress. With their WordPress e-commerce themes, open your business instantly. Sell your products easily. All for FREE. So go ahead and try it out!

A very popular provider of e-commerce functionality for WordPress is WP e-commerce, which is a free bolt-on shopping cart that lets customers buy your products, services and digital downloads online. They’ve had over 750,000 downloads! They also offer some premium upgrades to have more features.

If you also interested to support our website, please go to BuySellAds.com and promote your service or product on WP Engineer. Maybe not this month, but maybe next month we have a spot just for you available.

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)

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.

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)

You need:

• a separate address for the unpaged archive,
• a filter for the internal WordPress query and
• a link to your ‘all posts’ page.

We put everything into a class to avoid name collisions and to keep the global namespace clean.
We name the file class.View_All_Posts.php.

Let’s start with the class, the parameter and a checker, this is easy:

class View_All_Posts
{
    /**
     * GET parameter to trigger a complete, not paged archive.
     * @var string
     */
    protected $all_param = 'all';

    /**
     * Are we there already?
     *
     * @return bool
     */
    public function is_all_posts()
    {
        return isset ( $_GET[$this->all_param] );
    }
}

For the address I use a very simple approach: a GET parameter named all. You may change the name here; just stay with ASCII chars from a—z. все_сообщения will get you in trouble!

Next we need a constructor that manages our work:

    public function __construct()
    {
        /* Register the query argument. */
        add_filter('query_vars', array ( $this, 'add_query_arg') );

        /* Hook into the query. */
        add_action('pre_get_posts', array ( $this, 'view_all_posts') );
    }

The constructor references two internal functions – add_query_arg() and view_all_posts(), which we build next:

    /**
     * Registers the query arg in WordPress.
     * Otherwise it will be unset.
     *
     * @param  array $vars Already registered query args.
     * @return array
     */
    public function add_query_arg( array $vars )
    {
        return array_merge( $vars, array ( $this->query_arg ) );
    }

    /**
     * Alters the query to remove the paging.
     * @return void
     */
    public function view_all_posts()
    {
        if ( ! $this->is_all_posts() )
        {
            return;
        }

        $GLOBALS['wp_query']->query_vars['nopaging'] = TRUE;

        return;
    }

The first function just registers our GET parameter in WordPress. The second alters the query to the database and removes the paging.

We are almost done. A template tag for the link would be nice, wouldn’t it?

    /**
     * Creates the markup for the link.
     *
     * Usage in archive.php, category.php or search.php:
     * $GLOBALS['view_all_posts']->get_allposts_link();
     *
     * @param  string $text Linktext
     * @param  bool   $print echo or return
     * @return string|void
     */
    public function get_allposts_link(
        $text   = 'View all posts'
    ,   $before = '<p class="allpostslink">'
    ,   $after  = '</p>;'
    ,   $print  = TRUE
    )
    {
        if ( $this->is_all_posts()
         or $GLOBALS['wp_query']->found_posts <= get_option('posts_per_page')
        )
        {   // No link needed.
            return;
        }

        if ( isset ( $_SERVER['QUERY_STRING'] )
            && ! empty ( $_SERVER['QUERY_STRING'] )
        )
        {
            /* We have already visible GET parameters: /?hello=world. */
            $new_url = $_SERVER['REQUEST_URI'] . '&';
        }
        else
        {
            /* Note the difference: REQUEST_URL doesn't include
             * the query string while REQUEST_URI does. */
            $new_url = $_SERVER['REQUEST_URL'] . '?';
        }

        $link = "$before<a href='$new_url$this->all_param'>$text</a>$after";

        if ( $print )
        {
            print $link;
            return;
        }
        return $link;
    }

Note: $GLOBALS['wp_query']->found_posts holds the sum of all posts for a given query, not just for the current page. Useful if you want to print out the total number on a paged archive.

If you want to avoid duplicate content, hide the full archives from search engines in your header:

    /**
     * Prevents indexing from search engines.
     *
     * Add this as an action to 'wp_head'.
     *
     * @return void
     */
    public function meta_noindex()
    {
        if ( $this->is_all_posts() )
        {
             print '<meta name="robots" content="noindex">';
        }
    }

Our class is complete. Now we put an object of the class into the global namespace …

$GLOBALS['view_all_posts'] = new View_All_Posts;

… add an action to wp_head …

add_action(
    'wp_head'
,   array ( $GLOBALS['view_all_posts'], 'meta_noindex' )
);

… and include the file into the functions.php of our theme:

require_once dirname(__FILE__) . DIRECTORY_SEPARATOR
    . 'class.View_All_Posts.php';

In our archive templates (archive.php, category.php, search.php) we print the link:

$GLOBALS['view_all_posts']->get_allposts_link();

Done.

…

Oh, wait … maybe you want to see the full code? And a download link?

Here’s the link: Download class.View_All_Posts.php

The complete code:

/**
 * Adds a view all posts page to any query.
 * @author Thomas Scholz http://toscho.de
 * @version 1.1
 */
class View_All_Posts
{
    /**
     * GET parameter to trigger a complete, not paged archive.
     * @var string
     */
    protected $all_param = 'all';

    public function __construct()
    {
        /* Register the query argument. */
        add_filter('query_vars', array ( $this, 'add_query_arg') );

        /* Hook into the query. */
        add_action('pre_get_posts', array ( $this, 'view_all_posts') );
    }

    /**
     * Registers the query arg in WordPress.
     * Otherwise it will be unset.
     *
     * @param  array $vars Already registered query args.
     * @return array
     */
    public function add_query_arg( array $vars )
    {
        return array_merge( $vars, array ( $this->query_arg ) );
    }

    /**
     * Alters the query to remove the paging.
     * @return void
     */
    public function view_all_posts()
    {
        if ( ! $this->is_all_posts() )
        {
            return;
        }

        $GLOBALS['wp_query']->query_vars['nopaging'] = TRUE;

        return;
    }

    /**
     * Are we there already?
     *
     * @return bool
     */
    public function is_all_posts()
    {
        return isset ( $_GET[$this->all_param] );
    }

    /**
     * Creates the markup for the link.
     *
     * Usage in archive.php, category.php or search.php:
     * $GLOBALS['view_all_posts']->get_allposts_link();
     *
     * @param  string $text Linktext
     * @param  bool   $print echo or return
     * @return string|void
     */
    public function get_allposts_link(
        $text   = 'View all posts'
    ,   $before = '<p class="allpostslink">'
    ,   $after  = '</p>'
    ,   $print  = TRUE
    )
    {
        if ( $this->is_all_posts()
        or $GLOBALS['wp_query']->found_posts <= get_option('posts_per_page')
        )
        {   // No link needed.
            return;
        }

        if ( isset ( $_SERVER['QUERY_STRING'] )
            && ! empty ( $_SERVER['QUERY_STRING'] )
        )
        {
            /* We have already visible GET parameters: /?hello=world. */
            $new_url = $_SERVER['REQUEST_URI'] . '&';
        }
        else
        {
            /* Note the difference: REQUEST_URL doesn't include
             * the query string while REQUEST_URI does. */
            $new_url = $_SERVER['REQUEST_URL'] . '?';
        }

         $link = "$before<a href='$new_url$this->all_param'>$text</a>$after";

        if ( $print )
        {
            print $link;
            return;
        }
        return $link;
    }
}

$GLOBALS['view_all_posts'] = new View_All_Posts;

Mission completed. Any suggestions?

Guest Post

This post is written by Thomas Scholz toscho.de, a good friend of us and a web designer from Halle, Germany.

Thank you very much from our part to Thomas.

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)