Whilst it is designed to work within a child of Twenty Eleven, it should be possible to adapt the template to suit other themes. If you are using another theme, remember that you will need to replicate the html structure of your own theme within the template.

You can then save your new template as pageofposts.php, upload it to your theme and then assign the Page of Posts template to your new Page via the Page Template Dropdown.

• Create a title in the browser toolbar
• Provide a title for the page when it is bookmarked
• Display a title for the page in search-engine results

It make sense, therefore, to take some time to craft a good title in your WordPress site. In the vast majority of WordPress themes, the title is generated in the theme’s header.php template file. So you need to start by editing this file.

Some themes simply use something like:

<title><?php wp_title();?></title>

But that’s not nearly enough to generate a good title. What you want is code that generates informative, page-specific, titles. So try something like:

<title><?php global $page, $paged;
if ( $paged >= 2 || $page >= 2 ) $we_are_on = sprintf( __( ' (Page %s) ' ), max( $paged, $page ) );
else $we_are_on = '';

if( is_home () ) : printf(__( '%1$s%2$s on %3$s'), wp_title('', false), $we_are_on, get_bloginfo('name') );

elseif( is_search() ) :
if( trim( get_search_query() ) == '' )  printf(__('No search query entered on %1$s'), get_bloginfo('name') );
else printf( __( 'Search Results for \'%1$s\' on %2$s%3$s' ), trim(get_search_query() ), get_bloginfo('name'), $we_are_on );

elseif ( is_category() || is_author() ) : printf(__( '%1$s%2$s on %3$s' ), wp_title('', false), $we_are_on, get_bloginfo('name') );

elseif( is_tag() ) : printf( __('Entries tagged with \'%1$s\'%2$s on %3$s') , wp_title('', false), $we_are_on, get_bloginfo('name') );

elseif( is_archive() ) :
printf( __('Archives for %1$s%2$s on %3$s'), wp_title('', false), $we_are_on, get_bloginfo('name') );

elseif( is_404() ) : printf(__( 'Page not found on %1$s' ), get_bloginfo('name')  );

else : printf( __('%1$s%2$s'), wp_title(':',true, 'right'), get_bloginfo('name') );

endif;
?>
</title>

1. Upload your new gateway icon to your theme’s images folder.
2. Edit your theme’s function.php file in a plain text editor and add the following new function>

   function mythemes_icon_cash() {
   	$icon = array(
   		'path'=>get_stylesheet_directory(). '/images/cash.png',
   		'url'=>get_stylesheet_directory_uri(). '/images/cash.png'
   	);
   	return $icon;
   }
   add_filter('eshop_merchant_img_cash', 'mythemes_icon_cash');

There are also filters for each of the other gateway icons:

eshop_merchant_img_cash
eshop_merchant_img_bank
eshop_merchant_img_authorizenet
eshop_merchant_img_payson
eshop_merchant_img_paypal
eshop_merchant_img_ideallite
eshop_merchant_img_webtopay
eshop_merchant_img_ogone
eshop_merchant_img_epn

Enjoy!

<?php printf( __("Sorry - I couldn't find anything on %1$s%2$s%3$s", 'theme_name'), '<span>', $my_searchterm, '</span>');?>

From the test results, it seemed that $my_searchterm was not being escaped and that this was opening up an XSS-scripting hole. Yet $my_searchterm was escaped!

$my_searchterm = trim(get_search_query());

After much head scratching — including some in-depth research into using printf with HTML tags — I’d pretty much given up on finding the root cause and was about to remove the entire line when Otto came to the rescue.

I’d been looking in the wrong place. The isse wasn’t with $my_searchterm — it was with:

"Sorry - I couldn't find anything on '%1$s%2$s%3$s"

The standard type specifier for a string substitution when using printf or sprintf is $s (PHP documentation link).

However, in WordPress, $s has a special meaning — it’s the unescaped search query. By using double quotes in the printf, I had stopped $s from being used as a string substitution and, instead, it was being parsed by WordPress.

The solution? Switch to using single quotes.

<?php printf( __('Sorry - I couldn\'t find anything on %1$s%2$s%3$s', 'theme_name'), '<span>', $my_searchterm, '</span>');?>

Now $s isn’t parsed — it’s substituted.

All in all, I was pretty appalled at how easily I had opened up this particular security hole — despite being paranoid about sanitising generated output. I also can’t help thinking that the WP core devs weren’t having a good day when they decided to use $s for the search query — especially since printf and sprintf string substitutions are commonplace if you are trying to make a theme translation-ready. Something like $wp_s might have been far safer.

In the meantime, check your scripts for double-quote enclosed string substitutions or you might end up making the same mistake I did.

So rather than explaining how to create a child theme again… and again… and again, I’ve uploaded two new theme downloads – a Twenty Ten child theme & a Twenty Eleven child theme.

Please note that these downloadable child themes do not implement any changes. They are purely “blank slates” for you add your own customisations to.

Simply upload the themes to your WordPress site, activate one of them and start customising!

Apologies to anyone who was hit by this bug. Please update to the new version to correct the problem. Thanks also to the wordpress.org Theme Review Team who managed to get the new version into the Theme Repository within 24 hours of the updated version being submitted.

ZenLite Petal — a bright & juicy child theme for ZenLite with added Google Fonts!

As with ZenLite, this theme has full support for all WordPress post formats with the Dancing Script font used for Quote post formats. The Tangerine font is used for the main site heading whilst Post & Page headers use the Open Sans font.

ZenLite Citrus — a bright & juicy child theme for ZenLite with added Google Fonts!

As with ZenLite, this theme has full support for all WordPress post formats with the Dancing Script font used for Quote post formats. The Lobster font is used for the main site heading whilst Post & Page headers use the Open Sans font.

Thanks to stug2000 for bringing this to my attention. How everyone else managed to miss it over the last 8 months is completely beyond me!

All of the same functionality as its parent theme but with a blue skin. Hopefully, this is the first of a a range of child themes for ZenLite to be released over the next few weeks. The focus will be a range of different colours rather than any additional functionality as the theme appears to fulfil a particular need amongst users as a simple, single column, design.