I recently upgraded my blog software to the release candidate version of WordPress 3.0. I am very happy with how it performs, and am excited that WordPress and WordPress MU have merged. This will make the development process much easier, especially for those of us with WordPress MU sites.
There is one new “feature” that I don’t like, however. A new filter in version 3.0 will automatically change all instances of “Wordpress” (note the small “p”) in posts, titles, or comments to “WordPress”. While the later is technically the correct way to refer to the software, I philosophically do not like it when software changes the meaning of user’s words without their consent. How can one provide examples of mispellings? How can a blog owner ensure that the integrity of commenter’s remarks are left intact?
While a spelling assistant is nice at times, sometimes you need to break the rules.
I wrote a short plugin (actually, it is just three lines of code) to turn this filter off. You can download it from the WordPress plugin repository.
If you don’t feel like installing a plugin, you could delete the code associated with this filter in your WordPress install. Be sure to back up your files and datebase before you modify anything.
If you have any questions or comments, feel free to leave them below.
Welcome to tomlany.net, home of Tom Lany's radio jingles, the latest on Tom's web and journalism projects, and whatever else is on his mind. Tom grew up in the Minneapolis area and is now attending 
Just a quick test comment…. I have to make sure it is possible to say “Wordpress” here!
Pingback: Wordpress 3.0 fuerza a escribir bien WordPress | Ayuda WordPress
Pingback: Lowercase p, dangit!
Pingback: Lowercase p, dangit! | Joiner.ro - Indexare gratuita feed-uri RSS
Pingback: mastermute.com
There’s now another ticket about this on WordPress trac.
Pingback: Wordpress 3.0 fuerza a escribir bien WordPress | Todo bit
Much appreciated, thanks.
Ridiculous that my servers have to run the plugin code (trivial though it is) in order to avoid running some other code which is completely pointless, and breaks things for some people. Oh well.
I just upgraded my site to WordPress 3.0.1 and noticed that this plugin is broken. I have identified a fix and will update the plugin today or tomorrow.
The plugin has been updated to be compatible with WordPress 3.0.1. Please get an updated copy from the WordPress plugin directory.
Let me know if anyone has any problems, comments, suggestions, etc.
Tom,
I love your plugin – it will be of great use to people whose site is getting badly mangled by a poorly thought out filter.
I’ve found a way to get a filter priority so that the problems you had between 3.0 and 3.0.1 can be coded around. Please find it below.
foreach ( array('the_content', 'the_title', 'comment_text') as $filter ) {
$priority = has_filter($filter, 'capital_P_dangit');
if ( $priority !== false ) {
remove_filter( $filter, 'capital_P_dangit, $priority);
}
}
Thanks for the note, Matt!
This looks like a better way to filter out the priorities, so the plugin isn’t trying to remove a nonexistent filter (or filter with a designated priority level). I will take a look at this soon and might update the plugin when I get a chance.
Thanks again!
hi, i hope you can help? (pretty please)
on my clients site it removes all lowercase p in the content. i installed the plugin and it didn’t work.
http://www.harleystreetcoaching.org.uk/index.php/
thanks
chris
Looks like all of the p’s are there now. Could you detail the problem further?