Getting a little P’veed

8 July 2010 in Rants, Web Design

This post was written after reading Justin Tadlock post on changing peoples content via the filter capital_p_dangit() php filter you can read his full post here. I very much agree with it and prompted to write this post after reading this one section.

The real issue is not the bug; it’s the display of content that people didn’t write. Sure, the cases where people actually intend to misspell WordPress are rare, but that’s besides the point.
~ Justin Tadlock

I very rarely dis-agree with the WordPress core team. But I feel you really lost your way with changing my content via capital_P_dangit(). It is not what you did but how you did it.

If you have written, posted, educated and informed, I would have said “Great idea Ma.tt”

But doing this without knowledge or consent and then is breaking across a lot of sites is an unfortunate and unusual lack of foresight on the part of the WordPress team.

(In writing this even the WordPress owned After the Deadline shows WordPress as a spelling mistake ~they fix that )

Also what goes on in WordPress.com is different then what happens on WordPress self hosted sites. You control everything on WordPress.com from the server to the permissions and ultimately you can fix everything. This is just not the case across the world of servers that run WordPress.

I am certainly not as gifted in programming as the WordPress team is, but I certainly see a need for improvement in communication and usability between developer(s) and designers in this regard.

Update: It is nice to see that the WordPress core team still has a sense of humour on the subject.

8 July 2010 Rants, Web Design

1 Comment to Getting a little P’veed

Unfortunately, the release announcement would have been a bit drawn out if we included every feature and bug fix. I don’t remember them all, and if you showed me them at random and asked me if I wrote it or committed it, I’d probably get the answer wrong half the time.

Here’s what I have an exception with. Every single change is “publicized,” particularly for the benefit of developers. There’s a mailing list that sends out every one of them as they happen (diffs included). There is a timeline on Trac with major activity including commits, and an RSS feed. You can even CC yourself on tickets you are interested in, or query for tickets and even use an RSS feed of the results.

And if you want to read every single patch and comment, there’s a separate mailing list for that too.

I’ll wait while you browse through the 2700 commits that went into WordPress 3.0 and you can let me know what else you objected to.