7 thoughts on “Lowercase p, dangit! WordPress Controversy Leave a comment

  1. Isn’t there bigger fish to fry than this? Seems like I notice a lot of time being wasted this on this discussion every time I poke my head up from my WordPress dev.

    Surely there are lots and lots of great new features of WordPress that could be moved forward instead!

    ..and now, back to the dev. 🙂

    1. I think if a core changes breaks peoples websites, especially over something so trivial, then it’s definitely worth spending time on.

      More than the fact that this is so small is the fact that they made a core change, that affects many people, and didn’t discuss the possible effects beforehand.

      1. I am just not sure why they focussed on such a small issue, now, when there are lots of ‘goodies’ people want to see added to WordPress to keep the machine rolling on! Lets not stall now!!

      2. Do you mean “isn’t there bigger fish for WordPress to fry”?

        In that case I absolutely agree. I think it’s a silly feature that’s caused a lot of negative publicity and confusion from the hardcore/ dedicated users. I suspect a lot of WordPress users simply didn’t notice, but I would also guess it caused problems for a lot more people than they had considered.

  2. It’s a small thing and the function itself is a perfectly decent idea, but it was the way it was implemented that’s annoyed a lot of people, myself included. It’s the fact it actually edits your content and was just snuck in that’s the problem. First this trivial matter, but what next?

Leave a Reply

Your email address will not be published.