[wp-trac] [WordPress Trac] #10452: Wordpress pollutes POST data

[WordPress Trac]

#10452: Wordpress pollutes POST data
----------------------------------------------------+-----------------------
 Reporter:  bilge                                   |        Owner:          
     Type:  defect (bug)                            |       Status:  reopened
 Priority:  high                                    |    Milestone:          
Component:  General                                 |      Version:  2.8.2   
 Severity:  critical                                |   Resolution:          
 Keywords:  post data pollution cancer abomination  |  
----------------------------------------------------+-----------------------

Comment(by bilge):

 Wordpress contributors have not earned any respect. Do you honestly expect
 to get away with such gut wrenchingly awful code, and not only that, but
 after having your attention raised to the most dire of problems stemming
 from your collective incompetence, close the only ticket that could
 actually be the first step towards salvaging this mess with the resolution
 "won't fix"? Were you expecting to be '''commended''' for that?

 I got into Wordpress for how it looked on the surface. I should have been
 mindful that beauty is so often only ever skin deep. Since installing it,
 it has been nothing but a world of pain because of issues exactly like
 this (and others, such as polluting the global namespace) which if not
 rectified will force me to move to another platform.

 You may think that my attitude is foul, but if you remove me, the stench
 won't go away. The stench is here because I'm doing the dirty work of
 unearthing some of the fundamental flaws in your software and you're
 getting offended because you can't stand to see the sight of them. It's
 about time someone corrected this mess and I don't mind if it starts with
 me. If you actually have the first clue about how your own code works then
 prove it and start fixing some of the things that are fundamentally wrong
 with it, starting with this ticket.

 There are many ways to address issues of backwards compatibility. Add an
 option for new plug-ins to subscribe to the raw POST data and provide
 escaped output to the old plug-ins if that's what it takes. It shouldn't
 be up to me to make suggestions on how to implement fixes: my
 responsibility ends with reporting bugs and providing feedback to clarify
 said reports. The onus is now on yourselves to come up with the best
 solution for this fine mess you've gotten yourselves into, and not to
 sweep it back under the rug.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/10452#comment:6>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software