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.

And I did a double-take too when I saw this posted in the wordpress.org support forums. I thought that this kind of thing was an urban myth. But — hand on heart — someone really did decide to store more than a dozen, previously published, posts in their WordPress Trash until they got around to polishing them up for re-publication.

When they finally logged back in again (weeks later), lo and behold, all of their precious posts had been permanently deleted with absolutely no chance of getting them back (short of restoring the whole site via a recent database backup).

Yes, folks, WordPress does empty your Trash for you every 30 days by default. That said, Trash is no place to store anything (unless you are one of these strange Windows users who also stores documents in their Recycle Bin in which case… you’re on your own).

If you want to pull posts off your site for further work or review, simply change their status from Published to Draft or Pending Review via the Quick Edit link or by Edit Post (or Edit Page).

Keep Trash for stuff that you really, really, don’t want any more.

Just edit the relevant theme template file and replace:

<?php the_content();?>

with:

<?php the_content('', false,'');?>

This will supress even the default “read more” link.

Next, move to the point in your template file where you want your custom “read more ” link to be displayed and add:

<a class="more-link" href="<?php the_permalink();?>#more-<?php echo $post->ID;?>"><?php _e('Continue reading );the_title();?></a>

Simple!

1. Using <?php the_content();?> in your theme template file(s) and then inserting the <!-- more--> into your post at your desired cut-off point.
2. Using <?php the_excerpt();?&gt; in your theme template file(s) and allowing WordPress to generate a teaser from the first 55 words of the post’s content — without the need to place a <!-- more--> tag in the post.

Option 1 automatically creates a nice “read more” link at the bottom of each teaser that allows readers to go straight to the full, single, post but it does mean that you have to remember to enter that pesky <!-- more--> tag into your posts before you publish them.

Option 2 is fully automatic but lacks the nice “read more” link. So how can you have all of the benefits of the automatic excerpt but also provide a link to the the single post?

Simply edit your theme’s functions.php file and add the following function after the opening <?php tag.

function my_excerpt_link() {
	return ' <a class="more-link" href="'. get_permalink() . '">' .  printf(__( 'Read $s'), get_the_title() ) . '</a>';
}
add_filter( 'excerpt_more', 'my_excerpt_link' );

The above code will generate an automatic link to the single post in the format:

Read Replace [...] with a Post Link

Now you get the benefits of both options.

Many visually-impaired screen reader users run their software in non-verbose mode — which ignores all title attributes. This is precisely because most web pages are overloaded with useless title tags. In screen reader software, a web page full of title attributes equates to way too much unwanted noise. This is especially so when you don’t bother to give your images nice human-readable titles.

Would you want to read a page littered with meaningless text such as “dcs3005-674.png”? Neither do screen reader users.

In this respect, WordPress has gotten it wrong. Title attributes should not be added to inserted images by default. There’s simply no real need for them amongst sighted users and (with luck) many screen reader users won’t even get to hear them.

If you have important info that you need to relay to screen reader users, then use the Alternate Text field to add a meaningful alt attribute to your images. That’s what it is there for. If you need to relay additional image information to your sighted readers (including non-mouse users), use the Caption field.

Installation

Upload the plugin to your blog, activate it and sit back. The plugin will do the rest.

Notes

The plugin is suitable for WordPress 3.2 & above. Tested in WordPress 3.3.

If you have already inserted images into posts, the plugin will not touch them. You’ll have to remove the title attribute manually by editing the image markup in each post within the HTML Editor. The plugin will only remove the title attribute from images that you insert after it has been activated and then only at the point of insertion. This means that it will have absolutely zero impact on the performance of the front end of your site — unlike some similar plugins that parse every single post just prior to display.

Download

These classes can be used — in conjunction with your theme’s stylesheet — to display different backgrounds on different pages.

Let’s assume your header.php template file contains:

<body <?php body_class(); ?>>

And your current CSS for the background looks like:

body {background:#fff url(images/bg.jpg);}

In a single post, your body tag would look like:

<body class="single single-post postid-188 single-format-standard logged-in admin-bar">

A category page could have:

<body class="archive category category-cat-a category-9 logged-in admin-bar">

whilst a tag page might generate:

<body class="archive tag tag-tag1 tag-92 logged-in admin-bar">

The CSS

You can add some new rules to your theme’s CSS to target specific backgrounds at particular pages.

Default Single Post

body.single {background:#ccc url(images/bg-single.jpg);}

Single Post with an ID of 188

body.postid-188 {background:#999 url(images/bg-special.jpg);}

Default Category Background

body.category {background:#eee url(images/bg-cat.jpg);}

Category A Only

body.category-cat-a {background:#ddd url(images/bg-cat-a.jpg);}

The possibilities are almost endless.

You can find a full list of the classes generated by the body_class() function in the WordPress Codex.

Step 1: Interpreting the Error Message

All of the relevant information is normally given in the first part of the message — the ... output started at... part.

Example 1

Warning: Cannot modify header information - headers already sent by (output started at /path/wp-content/plugins/foobar/foobar.php:8) in /path/wp-comments-post.php on line 55

In this example, the problem is in the foobar.php file of the Foobar plugin.

Example 2

Warning: Cannot modify header information - headers already sent by (output started at /path/wp-content/themes/wibble/functions.php:11) in /path/wp-includes/pluggable.php on line 850

Here, the problem is in functions.php file within the Wibble theme

Example 3

Warning: Cannot modify header information - headers already sent by (output started at /path/blog/wp-config.php:82) in /path/blog/wp-login.php on line 42

The problem is at line 82 of wp-config.php.

Step 2: Fixing the Problem

Example 1: A Plugin

The easiest option here is to simply delete the plugin and look for an alternative one. If you cannot access your WordPress dashboard, reset the plugins folder. Then re-install your plugins — with the exception of the one that caused the problem.

Example 2: The Theme

If you are not comfortable with editing PHP files, then you may want to look at installing another theme. If you cannot access your WordPress dashboard, switch to the default theme by renaming your current theme’s folder in wp-content/themes and adding “-old” to the end of the folder name using FTP or whatever file management application your host provides. This should allow you back into your dashboard where you can download another theme.

If you are comfortable with editing PHP files, then download the file mentioned in the error message (functions.php in the Example 2) and follow the instructions for removing invisible characters in a file.

Example 3: wp-config.php

1. Download wp-config.php from your site’s main WordPress folder.
2. Open the file in a plain text editor.
3. Check that the very first characters are <?php
4. If the very last characters are ?>, remove them.
5. Check that there are no invisible characters in the file.
6. Re-upload the amended file.

Removing Invisible Characters in a File

1. Open the file in a plain text editor.
2. Place the cursor before the first character in the file.
3. Press the BACKSPACE key & keep it pressed for a count of 10.
4. Place the cursor after the last character in the file.
5. Now press the DELETE key on your computer & keep it pressed for a count of 10.
6. Save the file without pressing any other key.
7. Check the encoding of the file. Do not encode files as UTF-8 with BOM. The BOM will be seen as a character.

• 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!

Cause: You do not have sufficient memory allocated to PHP within your hosting account.

There are a number of ways you can get your site up & running again. The method that works for you will depend upon your host’s server set up.

Via a php.ini file

Some hosts allow you to amend some PHP variables on your hosting account via a php.ini file. If necessary, check with your hosts to see is this option is available to you.

If you already have a php.ini file, download it and open in in a plain text editor. Look for memory_limit. If the value is 32M try, 64M. If it’s already 64M, try 128M:

memory_limit = 128M;

Then upload the amended file.

If you do not have an php.ini file, check with your host regarding first about creating it.

Via an .htaccess file

If you don’t have access to php.ini, you could try increasing PHP memory via an .htaccess file. If you do not have an .htaccess file in your domain’s root folder, you’ll first need to create one by creating a new file in a plain text editor and adding:

php_value memory_limit 64M

You may run into problems with saving the file. Because .htaccess is a strange file name (the file actually has no name but a 8 letter file extension), it may not be accepted on certain systems (e.g. Windows). With most operating systems, however, all you need to do is to save the file by entering the name as ".htaccess" (including the quotes). If this doesn’t work, you will need to name it something else (e.g. htaccess.txt), upload it to the domain root folder and then rename it using an FTP program

Via the wp-config.php file

Download your WordPress wp-config.php file and open it in a plain text editor and add:

define('WP_MEMORY_LIMIT', '64M');

immediately after:

define ('WPLANG', '');

Then re-upload the changed file.

Nothing works!

The methods listed above amy not work with all hosts. If you’ve tried them all and you’re still getting fatal error messages, try contacting your hosts for assistance. Just remember to send them a copy of the complete error message and tell them what you have tried so far.

My hosts won’t help

If your hosts insist on limiting your PHP memory allocation to less than 32M, change hosts. You really can’t run WordPress 3 or above without access to at least 32M.

If you are limited to 32M, it is still possible to run WordPress effectively but you will have to severely limit the number of plugins you use. I’d also suggest that you steer clear of plugins that parse Post or Page content in either the front or back end of the site as these plugins are likely to be the most memory-hungry.

Start by deactivating all plugins, then re-activate them again one-by-one until you hit the same problem. This should give you some idea of how many — or which — plugins you can safely use. Repeat the mass plugin deactivation again but, this time, only activate those that you have determined to be “safe”.

Good luck!