If you are not using a custom menu in the Lower menu location, the title of any Post marked as ‘sticky’ will automatically be displayed in the lower horizontal menu — maximising the visibility of all of your important Posts across your site.

View & download FlipFlop

The theme also boasts no less than 6 header images — with on-hover changes — so that you further customise your site. Or use the “Random” option to show a different header image on every page.

Fruit Juice details, screenshots & download.

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.

1. Edit theme template files
2. Upload a text file containing your quotes via FTP

So, the other day, I decided to update it.

Witty2 uses a shortcode, so you can add a random quotes to your Posts or Pages on a completely ad-hoc basis. The file containing the quotes is now stored in the plugin folder, so it can be editing via Plugins → Editor.

As with the original plugin, it still assumes 1 quote per line but it does allow a sub-set of HTML tags to be used — specifically br, em, strong and cite. The random quote output is generated inside blockquote tags, so you should be able to style it via your theme’s CSS, if necessary.

To add the shortcode to a template file, use <?php echo do_shortcode('[witty2]');?>.

Enjoy!

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.