148 Responses

  1. Andreas Nurbo
    Andreas Nurbo Published |

    Excellent writing, just excellent. I don’t think it can be written any clearer. Its one of those problems of either you get it or you don’t.

  2. Peter Westwood
    Peter Westwood Published |

    While I respect your strong opinions on the subject I find it troubling that you think that this isn’t doing a disservice to your plugin users.

    Including code in a plugin which isn’t relevant to the plugins functionality isn’t a nice thing to do – plugins should be contained and obvious in what they do.

    I guess you are going to add this feature to the description and readme for all your plugins?

    1. Andreas Nurbo
      Andreas Nurbo Published |

      I think we can call it civil disobedience. Since talking hasn’t worked what else are people suppose to do? Just lay down and stop caring?
      Westi, how do you think these matters should be handled by the community?
      I really want to know.

    2. Kevinjohn Gallagher
      Kevinjohn Gallagher Published |

      Including code in a plugin which isn’t relevant to the plugins functionality isn’t a nice thing to do…

      Peter, could the same not be said of the Core?
      Is coding functionality that isn’t relevant to the action any more benfitial, or any less worrying?

      As someone who codes and names files and links purely lower case ( am highly dyslexic and it makes life alot easier for me ), this has caused untold issues over a number of my websites.

      I suppose my question here is, How is this change/code benfitial to the people who will use it? While there are plenty of features and functionality in WordPress that I do not use, I can see their benefit to some people. Can I ask, which users benefit from this change?

      I guess you are going to add this feature to the description and readme for all your plugins?

      If only someone had done this at AutoMattic (http://core.trac.wordpress.org/changeset/14996) maybe we might have caught this before it went live.

    3. Chip Bennett
      Chip Bennett Published |


      While I respect your strong opinions on the subject I find it troubling that you think that [the capital_P_dangit filter] isn’t doing a disservice to [the WordPress community].

      Including code in [core] which isn’t relevant to [core] functionality isn’t a nice thing to do – [core] should be contained and obvious in what [it does].

      I guess you are going to add this feature to the description and readme for [core]?

      …there, fixed it for ya!

  3. Cristian
    Cristian Published |

    Committing something without a Track ticket is rather annoying to say the least.

    I’m going to update all my Child Themes to remove this filter.

  4. Kevinjohn Gallagher
    Kevinjohn Gallagher Published |

    Vote with your feet? This type of remark represents one of the biggest issues in the WordPress community. Attitudes like this can bring down entire empires.

    It did with bbPress.

    I am reminded of one Pig saying something similar to another Pig called Snowball… If only there was a moral in Orwell’s Animal Farm that would be relevant here…

    Don’t let their voices go unheard

    Justin we have been heard. Look at Matt’s comments here:

    The more trivial the topic, the more people
    likely to have an opinion, because it’s easier to do so.

    The fundamental flaw of mailing lists, and arguments like this thread,
    is that they come to be dominated in volume by the people who have the
    most time to post to them.

    Apparently, those of us who promote and work with WordPress every day; and are active in attempting to give back, are only welcome when we are being sycophant.

    I’m not sure about anyone else, but for me this attitude has really started to permiate through from some folks Automattic in the past year (way more so than in the past) where the humble nature of the people there was always something I revered highly.


    While we’re at it:

    There is no such thing as a “plugin”, it’s “plug-in”. I look forward to someone being anal pedantic about that and watching all the URLs and Slugs that it breaks.

    Oh and my favourite:

    There is NO capitalisation for any non-religious words in Arabic. At all. So if like some of my users you write for a non-nativly-english-speaking audience you’re actually outputting text that is 1) wrong and 2) could easily be percieved as Blasphemous.

    If someone get hit by a thrown shoe, will that count as someone “voting with their feet”?

    Im’ so glad that these sorts of things were all considered. Otherwise it would look like a really daft change to add into the Core…

    1. Mano Cornuto
      Mano Cornuto Published |

      If someone get hit by a thrown shoe, will that count as someone “voting with their feet”?


      PS: Shouldn’t that be KevinJohn? Capital J, dangit!

      1. Kevinjohn Gallagher
        Kevinjohn Gallagher Published |

        haha, oddly no. It’s “Kevinjohn”.

        I’m actually Kevinjohn Anthony Nora Gallagher ( with the Anthony pronouced “Ant-nay” and Gallagher pronouced “Gôl-a-her” ).

        Glad you had a chuckle mate, it was written with tongue firmly in cheek 🙂

  5. J. Bear Savo
    J. Bear Savo Published |


    When I installed WP on my site via GoDaddy, I just used the default GoDaddy subdirectory:


    Are you saying that this new filter can cause problems with my site? If so, will the plugin correct this?

  6. Jan Egbert
    Jan Egbert Published |

    Is capital_P_dangit() the WordPress 3.0 Easter Egg I’ve been looking for so eagerly? That would be a capital Disappointment.

    1. Thomas Clausen
      Thomas Clausen Published |

      It probably is. And all this time we were looking for it, and then the easter egg turns out to be a bug 🙁

  7. Daniel
    Daniel Published |


    Matt kind of “impose” this really silly code and now he is started to get “angry” of the community. I really don’t get it here.

    What’s up Matt?

    I’m believe that Matt’s intention was good. But we are all human, we make mistakes. Matt, just be humble and move on.


  8. Eugen
    Eugen Published |

    Well written and to the point. I was the one that asked you earlier on Twitter why wouldnt you write about it and I happy to see that you decided to do it.

    It’s a big deal and Matt’s attitude in the past year is going to piss off more and more people. Let people have their say, dont just impose something on them.

  9. The dangit filter :: BenjaminBradley.com
  10. Chip Bennett
    Chip Bennett Published |

    Again: credit to Jeffro at WPTavern for reminding me about Ozh’ plugin. I had completely forgotten about it.

    I have already added the filters to my own theme’s functions.php, but I downloaded/installed your plugin, to make my voice heard in terms of plugin download numbers.

    Of course, as Matt has already stated: our little petition-by-plugin needs to get 50,000 downloads for him to take it seriously. (Aren’t double standards grand!)

  11. jotrys
    jotrys Published |

    The question is:
    To P or not to p.

  12. Chip Bennett
    Chip Bennett Published |

    Oh, regarding the plugin-developer protest: if I were to do likewise, what is the best way to go about it? Should I just add the remove_filter calls, or should I check for their existence first? (Does making a remove_filter call for an already removed filter cause any breakage or noise?)

    I’m thinking I’m going to add this to my plugins, as well (enabled by default, with an option to disable).

    (I’ll also add it to any theme’s functions.php.)

  13. links for 2010-07-08 | Links | WereWP
  14. Kevinjohn Gallagher
    Kevinjohn Gallagher Published |

    @Chip & @Justin,

    Should we all attempt to use the same remove_filter calls (with option) in our plugins/themes? Perhaps a unified piece of code that we can advise other people to add to their plugins/themes.

    I feel that would give a stronger response than each of us writing out own; and make life easier for our users (who really are the victims here – “we” the people who are this involved with WordPress have the ability to remove the line of code).

    It might also alleviate some of the concerns that our plug-in/theme users have about such functionality; knowing that it wasn’t something that we undertook on our own nor without good reasoning.

    Your thoughts?

  15. Ray Gulick
    Ray Gulick Published |

    Absolutely impeccable argument; very well said. I hope Mullenweg (a week ago I would have referred to him as Matt, but now he seems less personable) reads it and a lightbulb clicks on.

  16. Loughlin
    Loughlin Published |

    What a load of rubbish. At a recent wordcamp a collegue of mine was presenting to a room full of people about an image plugin he had written and one of the wordpress people got upset he was using the wrong logo (the ‘fauxgo’) which completly ruined a point he was making about images and wordpress in general.

    I personally wanted to stab this person in the eyes for ruining the flow of a great presentation but I restrained myself. I appreciate how precious the creators of such a wonderful platform can be but this crap about ‘voting with your feet’ really gets me because this kind of attitude could destroy wordpress or at least it’s perception as an open and customisable blogging platform.

    Check out my next plugin ‘LoadOfShite-goddamit’ – it replaces the word ‘Matt’ with ‘Sap’

  17. How To Spell WordPress | Theme Lab
  18. Paul
    Paul Published |

    Thanks Justin for this post.
    Thanks for all the comments above.

    WP is opensource and it belongs to the community.
    No such desicion should go without asking the community.

    This ‘to p or not to P’ topic started me to question Matt’s attitude.
    ( I believe he is a nice guy, but this isn’t something I can agree with.)

    How could you forcefully edit how people want to write a word ?
    Even the government wouldn’t do this !

  19. Dickes P | elektroelch.de
    Dickes P | elektroelch.de at |
  20. Stop Taking The ‘P’ Already — Mark McWilliams
  21. Dave
    Dave Published |

    Thanks for taking a principled stand. Much as I admire Matt’s idealism, good ideas, hard work and dedication, I really think he needs to learn how to walk the walk where community is concerned. Those of us with one foot (or both feet) in WordPress.com are all too familiar with this aspect of his behavior. See for example how he has responded — or failed to respond — in the WordPress.com forums to the recent controversy over the new reblogging feature.

  22. Robert Dall
    Robert Dall Published |

    I could not agree more with what you have said Justin. So maybe I made a few mistakes in my spelling or WordPress. But adding something to the latest install that does it for you and changes my content is so wrong in so many places.

  23. Tom Jenkins
    Tom Jenkins Published |

    Thanks for mentioning what I perceive to be the real issue here.

    “The code was committed to WordPress without a Trac ticket, so it wasn’t left open to community discussion beforehand.”

    There simply cannot be a double standard for core vs. contributor developers. The above statement is the most powerful, yet overlooked issue.

  24. Patrick Daly
    Patrick Daly Published |

    I’ve been staying out of this debate as well, so I’ve missed a few things that were said that upset me enough to get involved.

    If you don’t like the filter, vote with your feet or with a plugin.

    — Matt M

    I thought voting took place before core commits — via, trac, IRC, mailing lists, forums, etc. If WordPress is truly open-source and community-centric, then why has that principle been stripped in this case?

    I agree that the misspelling of WordPress is awfully irritating, but education is a much better alternative than editing others’ content.

  25. Robert Dall
    Robert Dall Published |

    Even the WordPress owned After the Deadline shows WordPress as a spelling mistake.


    1. Johan
      Johan Published |

      It looks like they’ve “fixed” that now…

  26. Matt Hill
    Matt Hill Published |

    Wordpress doesn’t have a great history when it comes to listening to users, but this is the most absurd thing I have seen yet.

    I can understand people being precious over their brand, and I understand the irritation at seeing your product name spelled incorrectly, but the way it’s been handled in this case is exceedingly poor and underhand.

    Well done Justin on a great article. I hope your considered words reach Mr.Mullenweg and he has the humility to realise what a silly thing he’s done, and remove it forthwith.

  27. Dougal Campbell
    Dougal Campbell Published |

    Well, I was all set to get back to ignoring this topic as irrelevant (c.f., my “Putting the H in WordPress-Hackers” message), until I realized that it had been implemented in a way that could cause URL breakage.

    Seeing as how it doesn’t appear that they are going to remove the filter, I have at least contributed a patch that will help avoid damage.

  28. mastermute.com
    mastermute.com at |
  29. WordPress, Wordpress | Abraão Coelho
  30. Anne Dougherty
    Anne Dougherty Published |

    Thanks for an insightful argument, Justin. I wasn’t aware of this issue before it came across my Twitter feed but it does raise another interesting communications point: the whole lesson that corporations and non-profits have had to learn over the past 5 years is that once your “brand” is in the wild you have very little control over how people use it.

    Are the folks at WordPress going to try to control hash tags on Twitter?

    What about tags on Delicious or Digg?

    Yeah, it’s irritating when people don’t respect your branding but that is the way the social network forms.

  31. Pete
    Pete Published |

    The fact that this dangit thingy can break image url’s is alarming… I would have had NO IDEA how to fix this problem if it happened to one of my clients!

    I think it’s stupid to have this code inside WP knowing full well it may ruin some websites… really, really silly Matt

  32. that girl again
    that girl again Published |

    Help me out here. Why are people surprised by this? I get why they’re outraged (I wasn’t exactly overjoyed when they pulled the same stunt on wordpress.com) but when exactly was this golden age when Matt didn’t treat wordpress as his personal property and didn’t dismiss negative feedback as ‘noise’? I must have blinked and missed it.

    This is hardly the first time that core has fallen victim to one of Matt’s hobbyhorses, and it’s not going to be the last. I don’t even bother to blog this stuff anymore. It’s just the same thing over and over.

  33. Neil
    Neil Published |

    A few points…
    I think Matt is directing his lifelong frustration at people spelling his own surname wrong at the entire Wordpress community. If you can’t spell my name right then dangit you *WILL* spell Wordpress right.

    I have no real issue with the intended outcome of the filter, but like many above, I strongly object to a) the way this was implemented – no TRAC. b) modifying content written by users. c) Matt’s attitude to all this.

    Wordpress (deliberate lowercase ‘p’, ‘cos I can), has two spots where this filter would fit just perfectly. Either bundle it with all new installs/updates as a plugin, ala akismet, or stick it in Miscellaneous as an opt-in. Job done. Panic over. Peace returns.
    Lessons learned.
    It is very easy for Matt to take the high ground, but how am I to recover the lost development time for fixing broken sites? Where do I send that bill?
    For over thirty years people have spelled my own surname wrong. It frustrates me, but I get over it. If I could write a filter to stop it, would I. Nah, better things to do.

  34. Lowercase p, dangit! WordPress Controversy
  35. Andrew
    Andrew Published |

    It’s not good to impose things on people, you’ll just piss them off. Listen to what they are saying and cater to their needs and prioritize what is important. I hope he realizes this.

  36. hakre
    hakre Published |

    The 338th download was by me because I wanted to check the sourcecode (but not using it, as you may have guessed).

  37. MattPress Egomania | hakre on wordpress
  38. The Web Warlock
    The Web Warlock Published |

    Funniest thing is that the proper spelling is actually not “WordPress”.
    It’s WordPress®. It’s been stated in the wp-hackers thread that it’s a registered trademark, and so must be acknowledged as such.

  39. Demetris
    Demetris Published |

    That’s why it is never wise to support arbitrary decisions. Sometimes you do support such decisions because they come your way and you are tempted to forget that they are arbitrary and that you can never know what the arbitrary decision-making will bring next.

    But you learn that with time, after you have found yourself in environments that are influenced too much by arbitrary decisions and that require too much effort to get work done.

    To the issue at hand and its implications:

    What I always wish for WordPress, as a user of it and as a contributor to the project, is to see it attract better and better people. Incidents like this do not help attracting better people; what they do is drive away good people. It has happened before and it will happen again if nothing improves.

  40. Stephen Cronin
    Stephen Cronin Published |

    I probably shouldn’t get into this – but basically it’s censorship. Which is ironic given Matt’s ‘tough stance’ with governments who wanted WordPress.com to censor its users…

    1. Mark Jaquith
      Mark Jaquith Published |

      What about this comment that you just left? Was it censorship when WordPress changed your straight quotes into correctly curled quotes (five instances)? Was it censorship when WordPress combined your two hyphen‑minus characters into an en dash? Was it censorship when WordPress changed your sequence of three periods into an ellipsis?

      Contrast what you typed to what WordPress generated.

      All of those things changed your content, automatically, without your permission, and without any GUI option in Justin’s WordPress install to disable those automatic changes. Censorship?

      Of course I’m being rhetorical. Calling corrections* censorship is absurd. It is no less absurd when the capitalization of a single letter is called censorship. There is actual censorship going on all around the world at this very moment. I’m damn proud of the fact that WordPress is being used to publish content that makes governments around the world afraid of the citizens who publish it. I’m incredulous that people are making a fuss about a single character (which is only one of dozens of automatic corrections that WordPress makes). It’s free software that is easily extended (or crippled) by plugins. If the thought of going the rest of your life without misspelling WordPress it too much to bear, you have an easy out. Take it, take a deep breath, and try to pick your battles.

      * In this case, the correction from two hyphen‑minus characters to an en dash was a sideways correction. From the placement, it looks like you wanted an em dash, which WordPress will swap out for three hyphen‑minus characters. And if we’re really picking nits, it should have been a comma anyway. 🙂

      1. that girl again
        that girl again Published |

        Yeah, this is the argument I keep hearing from the devs: how this is all so painfully trivial and don’t you people have more important things to worry about than one capital letter?

        I made basically the same argument when the ‘feature’ was introduced on wordpress.com. I said then that people who cared that passionately about camelcasing the name needed to get out more. You guys like camelcase for no better reason than that it makes WP sound all funky and web 2.0 (which is ever so 2005, by the way). Could you not just be grateful for the fact that people think your software is worth blogging about, without having tantrums about their occasional failure to observe your disregard for the spelling and grammar conventions of standard English?

        The point at which the silly little filter started breaking stuff was the point at which you should have said ‘whoops, sorry, guess our easter egg was rotten’ and restored it to the plugin status it deserves, not started blithering on about edge cases and curly quotes. Honestly, sometimes you people are your own worst enemies.

      2. Mark Jaquith
        Mark Jaquith Published |

        Is it truly absurd for someone to have a different opinion?

        I didn’t say that. I said it was absurd to call this censorship. That’s a historically and politically charged word with a specific meaning that does not apply in this case. It is hyperbole.

        It’s something that’s been building up over the last couple of years. Mostly, it’s about communication, and the problem that has a lot of people riled up is Matt’s communication with the community on this.

        Then people should address that, directly. Making hyperbolic arguments about how the capital_P function is censorship, is contributing to oil spills, or is inciting terrorism doesn’t really advance an argument about poor communication! It rather sets it back, I’d say.

        I said then that people who cared that passionately about camelcasing the name needed to get out more.

        Sure. Guilty. I can be a bit of a pedant. I put a lot of work and thought into WordPress, and it annoys me when people type it incorrectly. The people who are annoyed by incorrect capitalization of WordPress are the people closest to core. We’re preconditioned to be pedantic about these things — it’s our “baby.”

        You guys like camelcase for no better reason than that it makes WP sound all funky and web 2.0 (which is ever so 2005, by the way).

        I’m generally keen to avoid naming gimmicks, as everyone is just going to bungle it. But it is what it is.

      3. Stephen R
        Stephen R Published |

        Mark —

        So… you’re having a party at your house. Somebody slips into your bedroom, picks up your wallet off your nightstand, and removes a dollar.

        Are you A-OK with this because it’s only a dollar?

        Or, as a matter of principle, would you be mad that somebody stole from you while a guest in your house?

        This is not, and has never been, about “the capitalization of a single letter”. It’s about changing the author’s writing without permission and without indication that you’re doing so.

        And no, as Justin himself said in the original post above, mere formatting (curly quotes, et al) is not the same thing. This was put in to scratch a personal itch, plain and simple.

  41. Paul
    Paul Published |

    @that girl again

    The ticket#4254 you posted above is from 3 year ago.

    I appreciate your comments, but this isn’t a place for voting.

    – Matt ( @ticket#4254 )

    I think that explained everything.

    1. Paul
      Paul Published |

      WP has never been driven by committee, or voting, and I personally think that approach tends to create bland, soulless software.
      – Matt ( @ticket#4254 )

      I went on and read more about Matt’s attitude, and I’m amazed.
      This is from 3 years ago !

      The ‘to p or not to P’ thingy is simply about one person’s attitude.

      I love wordpress because it’s opensource and from my understanding, it’s a community driven project, I can not bring myself to believe that the project’s leader actually said that line above – really.

      Maybe it’s time to give Joomla a try.

  42. Como desactivar el filtro capital_P_dangit() | Todo bit
  43. Flogging a dead P and other links: Friday Find | Premium BuddyPress Themes at BuddyDress
  44. Enk.
    Enk. Published |

    Great article..
    I just like this new ‘P’ update.. at least we now know the proper spelling and case-spelling of WordPress, eh.. 😛
    Btw, just wondering.. how did you write ‘Wordpress’ with small ‘p’ in the article and rest misspellings too ? 😀

  45. Daily Tip: How to Remove the Capital ‘P’ Function From WordPress 3.0 - WordPress MU and BuddyPress plugins, themes, support, tips and how to's
  46. WordPress schreibt sich selbst ‹ dreitehabee
  47. David Tierney
    David Tierney Published |

    Making a choice to insert code into the core that has the effect of, as Justin points out,

    “The code literally breaks things like URLs on some sites. For example, suppose you installed WordPress in a /Wordpress directory. That would cause all kinds of trouble with things like images.”

    as an attempt at controlled branding or for any reason that is clearly not serving the users or community who use WordPress was clearly misguided and acted upon. We all make mistakes, and I believe someone said it well earlier in this thread – at this point, the best thing for everyone, especially Matt, is to acknowledge a mistake was made, fix it, and move on.

  48. Jason
    Jason Published |

    If this stance was taken with turning ‘wp’ into ‘WP’, the multitude of broken sites would spell disaster.

  49. David Tierney
    David Tierney Published |

    …and choosing to disrespect and dis-hearten the very community that has fostered the success of WordPress by dismissing something that is obviously important to them does volumes more damage to the name WordPress than such a plugin could ever achieve by forcing the case change of a letter.

  50. mccormicky
    mccormicky Published |

    The filter changes Wordpress to WordPress. Not all instances; you can type wordpress and WorDPrEsS into the title field or WYSIWYG editor and the filter will ignore them. It’s called capital_P_dangit not capitol_W_dangit.

    I don’t use capitol letters when naming my folders or file names and the only time I can think of needing to use a filter to filter out capital_P_dangit is when I want to show that I can’t type Wordpress if I wanted to in a post about the filter.

  51. It’s Called WordPress And Don’t You Forget It!!
  52. Stephen R
    Stephen R Published |

    Regarding Matt’s “This is not a democracy” statement — I understand the point of this, and generally I actually agree with him. He gave a great illustration of this by referencing the settings screen of… I think it was OpenOffice — with a ridiculous number of tiny little preferences. To avoid this, Matt comes down very hard on suggestions of adding new preferences.

    Doesn’t directly apply to the matter at hand here, but I just wanted to get that out since several people have commented negatively on comments from Matt in this regard.

  53. Ed Nailor
    Ed Nailor Published |

    When I first saw the capital_P_dangit function, I laughed. I honestly thought it was funny, mostly the name of the function.

    I have seen over the past couple years where the misspelling of WordPress has become a point of irritation. As this is a trademarked name, and the name is being used on the software bearing the same name, I can see why Matt added this. Personally, I tend to agree with the idea.

    Sure, there is the argument you make here, that someone should not be able to change your text without your permission. I get that, and agree there too. However, this is a trademark name, and again being used on the software that bears its name. So that has to count for something.

    I was not aware of the URL issue though, so that does present some BIG potential problems, especially when blogs are updated to 3.0 and have for YEARS had “wordpress” in the URL. This would cause major trouble.

    My suggestion would be to keep the filter, however modify it to be optional like the smileys, ect. I would further suggest that the option be enabled by default, but be something that is easy to uncheck in the settings of WordPress if it causes problems, or as in the arguement you make here, you don’t want WordPress to correct the misspelling of its trademark name.

    Or another option would be to remove the filter on URL’s and links. Then those that don’t want the filter at all can plug it (with a plugin of course)!

    From what I am seeing, the biggest problem is the breaking of URLs, which can kill someone’s WordPress website. Matt, if you are reading this, don’t be so stuck on this point that you kill websites of long standing users. make it optional, or prevent the filter from effecting links and urls. Then the debate of editing content can be just that, without the breaking of websites!

    Just my thoughts on the matter.

    1. Kevinjohn Gallagher
      Kevinjohn Gallagher Published |

      Hi Ed,

      Wonderfully written reply. Just to clarify, Registerd Trademarks don’t have any ownership / difference to the way they are written.

      “The mark consists of standard characters without claim to any particular font, style, size, or color”


      This has nothing, at all, to do with trademark.
      It’s a personal iritiation, and y’know, I think everyone is ok with that. Mark J’s reasoning behind that listed above ring true.

      What we’re not ok with is this:

      1) Updating without a Trac ticket so that people would know about it
      2) The attitude afterwards
      3) It breaks images, links and functions.
      4) It changes content, with no option to disable.
      5) Matt says that people should vote with plugins – well there is a plugin with this functionality already – it has less than 350 downloads in 3 years.
      6) It causes issues in certain parts of the world (read:Arabic)
      7) It goes against the very GPL that Matt claims to love.

      “In this freedom, it is the user’s purpose that matters, not the developer’s purpose”


      As much as Wikipedia isn’t quite the dictionary allow me to hit you with two quotes:

      “Censorship is the suppression of speech or deletion of communicative material which may be considered objectionable, … or inconvenient”


      “Corporate censorship is the process by which editors in [corporations] intervene to disrupt the publishing of information”


      Now, I don’t think anyone here is suggesting that Automattic is/was intending on censoring our content. I don’t doubt this was intended as a nice little fix, and in honesty, wasn’t through through.
      But I ask you, does changing the content of what I write, does making my links not work, does making my images not display – retrospectively and without my knowledge or specific permission not constitute to censorship in line with the quotes above?

      Thats a personal judgement call, and everyone’s entitles to their own opinions. For me, its just a lot of small issues with it, all of which kind of scare me a little.

  54. WordPress is stupid - Content Management, development, rant, WordPress
  55. Jacques
    Jacques Published |

    Thanks Justin, both informed and informative, as always (by any standards).

    I (an end user, rather objectively) wish to add something else… Was this the most EFFECTIVE way to address the issue at hand? Is this method (alone, that is) actually preventing mis-spelling in general and – more importantly – communicating the (assumed) significance there-of?

    It does not alert the user/administrator to the matter in an pro-active and infomative way, and may even be considered by some to be an arbitrary (even annoyingly) marketing gimmick for lack of such notice, i.e. context, being provided.

    It certainly does not assist directly towards a consious correction by the WP (abbreviation to be disencouraged?) community in use elsewhere, e.g. emails, branding, marketing material, etc (i.e. non-post content), where the name has a far more significant (branding) profile within the IT and WP business client community. This would be true in particular while aggressively growing the user base within the design and development community whom will not have the insight of the “old school”, so some education would be in order.

    Furthermore, is the correction to URLs (my spelling, probably wrong) justified for branding purposes alone? And if URLs cannot be meaningfully excluded from such correction (via the chosen method), then surely, a inappropriate approach..?

    So, beyond the case relating to ethics, principle, community spirit, etc, I am suggesting that this is poor form by Matt from a goal-oriented, business perspective, and the fact that he defends it so vigorously reflects even more poorly on his strategic thinking. A very defensive stance for someone in his position, surely. Or is that position the very issue..?

    Harsh on Matt? Hope to hear from others as to whether I am perhaps missing the point…


  56. Wordpress Desrespeita Seus Usuários
    Wordpress Desrespeita Seus Usuários at |
  57. Mad Tomato
    Mad Tomato Published |

    I guess I should aPologize to Matt for all the tyPos I’ve made.

    Sorry, Matt. My bad. 😀

  58. Site5 Rebate
    Site5 Rebate Published |

    If you are going to comment about WordPress you can at least show respect for the company by using the proper formatting. It might be annoying, but it isn’t that big of deal.

    1. Chip Bennett
      Chip Bennett Published |

      Principles can be so inconvenient at times. Consider:

      “In this freedom, it is the user’s purpose that matters, not the developer’s purpose”

      So, please explain to me how it is acceptable, from a free-software-philosophy perspective, for ostensibly free software to force the developer’s purpose (capitalizing “WordPress” correctly, showing “respect” to the WordPress project, etc.) upon the user?

  59. Fix WordPress Capital P Dangit. What is it anyway?
  60. Ed Tiley
    Ed Tiley Published |


    There’s one aspect of this debate that nobody has touched on, and that is defense of trademarks. Under US law, the owner of a trademark must take all reasonable steps to defend the trademark from appropriation and misuse.

    If a trademark is genericized it makes it harder for a trademark owner to retain their rights. Aspirin, cellophane, and videotape are all examples of words that began life as trademarks, but are now so generic that the trademark is unenforceable.

    So, there may be a “corporate” reason behind this capitalization function that isn’t immediately evident to those engaged in this debate.

    I do, however, stand with you on the aspect of breaking URLs. Although I’m no lawyer, I don’t think the inclusion of a trademark in an URL would be grounds for a court to find a trademark invalid due to generization. The code should be changed so that it doesn’t affect URLs dangit(!).

    1. The Web Warlock
      The Web Warlock Published |

      @Ed Tiley,
      You’re quite right with:

      If a trademark is genericized it makes it harder for a trademark owner to retain their rights.

      And, indeed, having *the trademark owners* willingly, consistently and continually missing and failing to acknowledge the trademark as a trademark —that is, WordPress®— is the best way to get your trademark genericized. Hey, the owners themselves are forcing people into using the trademark as a proper noun, not a trademark!
      That was what I was implying in my previous reply —which you either didn’t read, or thought to be bot-made :). It’s been a bad, bad decision and management from the community point of view —but as for brand management and trademark defence, the “corporate” point of view, it’s much, much, much worse.

  61. Old Castle
    Old Castle Published |

    I “feel” sorry for Automattic’s employees that cannot express a different opinion because of the big boss is there.

    Who reads the core.trac can see that who defends this filter, do it without “conviction”. Maybe because they cannot express the real feelings.

    First was this filter, now Matt gets in trouble with Thesis

    What is next??

    Now, let’s relax http://www.youtube.com/watch?v=LaboUIpvxZA

  62. commentary « wordpress™ wank
    commentary « wordpress™ wank at |
  63. Jesse
    Jesse Published |

    Ya know, I’m not usually one to jump on the band wagon but this issue really irks me. I found 27 new 404’s on my site that were caused by this, so I removed the filters and life is good.. then I sat back and followed the comments from both sides on this until today when I was at Matts blog and guess what… in his footer he has WordPress as WORDPRESS… what a hypocrite, so yeah.. i went to the trouble of doing a screen cap just because things like that get to me lol… so heres a link if you want some humor with a dash of egomania..

    http://admindaily.com/images/egomatt.png so its saved for prosperity as I am about to mention it on his blog, please feel free to pass this around 😉

  64. Derek Herman
    Derek Herman Published |

    I’ve been building WordPress powered web sites for years now and like to think of myself as someone who has always supported WordPress and its community. However, lately the people in charge and the support team has made me really considered forking the code base or looking for a new application.

    A once extremely loyal community member hoping for a better WordPress.

  65. Rahul Bansal
    Rahul Bansal Published |

    As reader of your blog I read this post on the same day you published it.
    But today, I came across a very bad side-effect of this.
    Matt’s filter made many images and links on our blog as 404!
    we prefer lowercasing image names and now if images have “wordpress” in their name and so src value, they are changed to “WordPress” by this filter.
    While I like to spell “WordPress” as “WordPress” only, I really hate for this intrusion.
    -10 for Matt.

  66. Reading List: July 26th 2010
    Reading List: July 26th 2010 at |
  67. goto1o
    goto1o Published |

    Thanks for a great write-up Justin.

    There are a lot of great comments here too. I don’t have much to add, but I do want to show my support for the community.

    As someone who holds WP near and dear, I find this whole situation very disheartening. I can’t help but feel that WP may be sliding down a slippery slope.

    It’s the principle, dang it!

    Please make it right AutoMATTic.

    Somehow this whole fiasco flew under my radar, until today when I was searching to see if it was “dang it” or “dangit”. I prefer the latter, but it seems that the former is correct. Mainly, I just wanted to stave off the pedantic trolls.

    However, in the case of capital_P_dangit(), I’ll become a hypocrite.
    It’s “dang it”, dang it.

  68. Steve Nisbet
    Steve Nisbet Published |

    Excellent write-up Justin, hadn’t even realised this had crept into the code until I read your review. I had a period of time ranting on WPMU forums because of the decision to add code that would, effectively, cripple any site that utilised a www as part of its domain name. This was part of the movement no-www.org thinking, where essentially some blog writers feel forced into having a ‘www’ at the beginning of their domain names and want rid.

    Can’t claim to fully understand the point of the issue, as a very early adopter of the web I recall strongly how most stites opted for www to differentiate from other protocol services running at the same domain, very useful for management and scripting. Its now part of the idiom, people say www in every day language where once it meant nothing at all.

    If you want to buy into the campaign fine, but why release Open Source software that contains code that prevents a site with a www in the domain from working post installation. Is that going to endear me to your point of view or hack me off and make me want to use another piece of software. Indeed, if I wanted to use WPMU I had to hack the code in several places to allow me to use the software on my own domain name. Given the plethora of ‘www’ domains in the world vs the number without – not a market winner.

    To force control over spelling of one word instance isn’t something you will see in many packages anywhere, it saddens me that its crept (and lets be honest without a Trac ticket crept is the word) into the codebase with wreckless abandon on 404 (and others) like Rahul has experienced above.

    How many sites were destroyed or maimed before news of this wonder crept out?

    If Matt is so focused on this as a solution, why not code it better and have it regex for URL’s and ignore them?

    All in all, seems very, very petty and potentially very destructive.

    good on you for promoting the issue



  69. Ozh
    Ozh Published |

    Almost missed this post because I was on holidays when it went live, would have been a shame 🙂

    Nice rant. I must admit I find the whole debate on the trac ticket a bit depressing, and I just don’t understand why crappy code nobody wants doesn’t get reverted…

  70. Armand
    Armand Published |

    Just to let you know, for some reason when I read your article, the “P” is always capitalized. I also tried the remove filter code in functions.php but it didn’t work.
    Tom’s plugin does work though.

  71. Should your CMS be allowed to do that?
  72. Jody Hamilton
    Jody Hamilton Published |

    Beyond the content editing issue, I find some of the basics here to be really troubling:

    Code quality: The comment itself admits a violation of coding standards in choice of function name. It also does not include the standard @param and @return information. It doesn’t seem like WordPress core development is adhering to much of a quality process.

    Transparency: There was no issue created before this change was committed? So, some developers have direct commit access and this commit access is not immediately revoked when they commit changes without peer review? Beyond the completely broken nature of this community process, this seems like an enormous security problem.

    It sounds like the WordPress development problems go a lot deeper than capitalization.

    Also, why is it so hard just to find the function in WordPress’s source code? Maybe WordPress should use Drupal’s api module to create a proper api.wordpress.com

    2822   * Forever eliminate "Wordpress" from the planet (or at least the little bit we can influence).
    2823   *
    2824   * Violating our coding standards for a good function name.
    2825   *
    2826   * @since 3.0.0
    2827   */
    2829  function capital_P_dangit( $text ) {
    2830      // Simple replacement for titles
    2831      if ( 'the_title' === current_filter() )
    2832          return str_replace( 'Wordpress', 'WordPress', $text );
    2833      // Still here? Use the more judicious replacement
    2834      static $dblq = false;
    2835      if ( false === $dblq )
    2836          $dblq = _x('“', 'opening curly quote');
    2837      return str_replace(
    2838          array( ' Wordpress', '‘Wordpress', $dblq . 'Wordpress', '>Wordpress', '(Wordpress' ),
    2839          array( ' WordPress', '‘WordPress', $dblq . 'WordPress', '>WordPress', '(WordPress' ),
    2840      $text );
    2842  }
    2844  ?>
  73. After ThesisWP-Gate It’s Time for the WordPress Foundation to Grow Up | The Blog Herald
  74. Images not resizing? What?!
    Images not resizing? What?! at |
  75. Ash
    Ash Published |

    Spot on. No one has the right to modify your content except you.

  76. How to Remove the Capital “P” Function From WordPress 3.0 | dressyourwp.com
  77. Chris Ames
    Chris Ames Published |

    hi, i hope you can help?

    on my clients site it removes all lowercase p in the content. i installed the plugin and it didn’t work.



  78. Chris Ames
    Chris Ames Published |

    with regards to my previous post, i just tried all the remove filters and that didn’t work either.

    has anyone had this problem?

  79. PatJ
    PatJ Published |

    So if I write:
    Using Microsoft Word press reporters can edit….
    will it become
    Using Microsoft WordPress reporters can edit….

    oh it’s just another MS product then 🙂

  80. Maksym Kozub
    Maksym Kozub Published |

    “Vote with your feet”? OK, that is what I have done. I had recently got my Windows Live Spaces blog transferred to wordpress.com, and I did like their software so much as to tart making plans to use it on my site. However, yesterday I read the whole story about this issue (i.e. capitalization automatically forced by the core), I killed my blog, leaving the following note at wordpress.com:
    I have just read all Matt Mullenweg’s messages, as well as those by Andrew Nacin, and other entries in various discussions on the capital_P_dangit filter. Before that, I was going to download WordPress, install it, and use it for my new website. Now, however, I am not going to use WordPress for my website, nor publish anything here at wordpress.com. I am literate enough on the technical side, so I would be able to remove the filter if I were to use the software on my website; however, this is a matter of principle in my view. Guys, you have made a fundamentally wrong move.

    Maksym Kozub

    (For the record, I did not even use that word in my blog, not in any URLs etc., so I was not directly affected by this change in their software. Voting against this tacit implementation of capitalization has been a matter of principle for me.)

  81. Top 10 Functions for functions.php | Interconnect IT - WordPress Consultants, Web Development and Web Design
  82. huyz
    huyz Published |

    This obsessiveness with spelling of WordPress is pretty short-sighted. If people want to write it Wordpress, that’s a good thing! It means that Wordpress is joining the lexicon on equal footing with Word and Press. Man, how ridiculous would it be if Microsoft insisted on Micro-Soft and yahoo changed all their users’ emails and IMs so that they spelled “Yahoo!” with the exclamation mark. Or if Google insisted that people not use their name as a verb.

    If Wordpress is considered a single word and capitalized as such, it means that the branding is succeeding. Rejoice. Don’t be anal.

    In any case, we DO NOT need *more* code; we need faster sites. If the author feels successful enough that he has carte blanche to do silly things, then WordPress has jumped the shark.

  83. WordPressing its Luck « COM585
    WordPressing its Luck « COM585 at |
  84. Wordpress richtig schreiben – auch in Wordpress – Sebastians Blog
  85. скачать фильм, скачать кино, смотреть фильм, смотреть кино
  86. скачать фильм, скачать кино, скачать ужасы, скачать комедию
  87. Intriguing Interview With Matt Mullenweg By Japanese Magazine
  88. WordPress And Government
    WordPress And Government at |
  89. What `the_content` goes through
    What `the_content` goes through at |
  90. It’s spelled WordPress, not WordPress | SheaPress
  91. It's spelled WordPress, not Wordpress - SheaPress
  92. How To Become A Top WordPress Professional | WordPress Planet
  93. Today’s Links | JohnAspinall.co.uk
    Today’s Links | JohnAspinall.co.uk at |
  94. Das eregierte Binnen-P: Aus “WordPress” wieder “Wordpress” machen | Hart gerockt
  95. Priyank
    Priyank Published |

    I think WordPress must be proper in this case.

  96. Wordpress schreibt sich selbst - mkln.org
  97. Cum să cenzurezi anumite cuvinte în WordPress | Eugen Păun
  98. Hooray! WordPress for Android updated | 7StarApps.com
  99. How To Become A Top WordPress Professional | NETLABB
  100. Nikhil Singh
    Nikhil Singh Published |

    I think WordPress should be proper?

  101. A
    A Published |

    Just saw “capital_P_dangit” mentioned in the WP3.8 changelog (http://codex.wordpress.org/Version_3.8) and wondered what the current status is. Where is it used nowadays?

  102. WordPress, Openness, and Communication
    WordPress, Openness, and Communication at |
  103. Carlo Rizzante
    Carlo Rizzante Published |

    Thanks for a great post, Justin.

    I adopted your solution in all the themes I develop. Of course my customers are free to let the capital_P_dangit() do its job, if so they prefer. But the default so far is to remove the filter as you elegantly displayed on this page.

    Stay cool.

  104. Passion For Excellence | How To Become A Top WordPress Professional
  105. How to Become a Top WordPress Professional
  106. Why is the P in WordPress Important? | ClarkWP WordPress Magazine
  107. Web Writing: The Editorial Article | Learning from Lorelle
  108. Eight Hidden Gems in the WordPress Function Reference - The Infinite Studio
  109. Eight Hidden Gems in the WordPress Function Reference | Orbit2 Website Design Leeds
  110. Eight Hidden Gems in the WordPress Function Reference | Your Web App
  111. Eight Hidden Gems in the WordPress Function Reference | Tech Tips
  112. Hur stavas WordPress? - Kenth Hagström
    Hur stavas WordPress? - Kenth Hagström at |
  113. How to Restore the Link Title Attribute Removed in WordPress 4.2 - WPMU DEV
  114. How to Restore the Link Title Attribute Removed in WordPress 4.2 · Clisr
  115. WordPress Customizer - the good, the bad and the ugly - Andreas Nurbo
  116. How to Become a Top WordPress Professional
    How to Become a Top WordPress Professional at |

Comments are closed.