Remove capital_P_dangit content filter

[discobot]

I don’t really have strong feelings about this one but I know that others do.

This petition is for removing the capital_P_dangit function that forces WordPress (now ClassicPress) to always be displayed with a capital P.

Like other removed features, I think we should make this (yes, even this) into a core plugin that people can disable if they want.

Pro capital_P_dangit

Many people unintentionally write Wordpress, but this looks unprofessional. Whether WordPress or ClassicPress, it’s important to preserve the project’s brand and present it consistently.

Anti capital_P_dangit

• “Don’t mess with my content”
• Early versions of capital_P_dangit had performance and correctness issues, but as far as I know these have been fixed.

 
Anything else?

Feel free to discuss below.

Previously: Remove capital_P_dangit() function · Issue #180 · ClassicPress/ClassicPress · GitHub

---

Read-only archive: Issues · ClassicPress/ClassicPress · GitHub

Author: James Nylen

Vote count: 10

Status: open

Tags:

• request-remove-feature
• request-modify-feature
• difficulty-easy

---

Comments

I’m on the fence with this one as I understand and feel for both pros and cons. As someone who hardly ever writes it wrong, I tend to be in the “don’t mess with my content”-camp, so I’m giving this a little vote up.

~ posted by Pieter Bos

When it comes to the CP name, especially in these early days, I think it behooves the project to make the correction, simply from an identity standpoint. While I didn’t agree with how the function was forced on everyone, I did understand the reasoning for wanting it in place.

Same as Pieter, I tend to get it right, but surely I’ve made an error here and there. In those cases, I’d like it to be corrected. As a consumer in the WP space, I have always avoided products and services offered by those who get the capitalization wrong because it speaks to a lack of attention to detail, at the very least…and I definitely don’t want that to be a perception of my “shop” if I made a simple mistake.

OTOH, there’s a certain irony in making the software name look more professional by running it through a function that looks like it was named during a temper tantrum.

So, my vote is to keep it. …just wish it would be renamed in a professional manner.

~ posted by Code Potent

Amusingly, renaming the function would break any existing plugins that disable it.

~ posted by James Nylen

Can we keep it but rename it then? I agree with CodePotent that it’s important to keep looking professional. Changing its name to something more professional would align with that. And I don’t mind breaking that tiny bit of plugin compatibility!

~ posted by Tim Kaye

i share the same option as Tim Kaye. set old name as deprecated, convert to a new one, without the useless suffix.

~ posted by Pedro de Carvalho

[viktor]

This is inline with our clean up of the core.

[Simone]

I’m for leaving in place the function (and optionally deprecate it) and don’t add the filters.
So anyone who feels the need can just plug it back.

foreach ( array( 'the_content', 'the_title', 'wp_title' ) as $filter )
	add_filter( $filter, 'capital_P_dangit', 11 );
add_filter( 'comment_text', 'capital_P_dangit', 31 );
add_filter( 'widget_text_content', 'capital_P_dangit', 11 );

Edit: reading around, about deprecation, it would be nice to deprecate it in favour of cp_brand_awareness() or something like.