[wp-hackers] Putting the P in WordPress
wphackers at jakemgold.myfastmail.com
Tue Jul 6 21:58:21 UTC 2010
Just to be clear, the specific issue of using "Wordpress" in a path or
image name /has/ been addressed in a patch (I think by Mark Jaquith) for
That's an overt "bug" that can break things. The philosophical debate
about the very inclusion of this filter is fascinating, but also strikes
me as "water under the bridge", particularly on a "hackers" thread.
As to the question of "bloat", one could also argue that constantly
checking a "fix Wordpress" option setting before applying a simple
filter is also adding bloat.
On 7/6/2010 1:30 PM, eric at eamann.com wrote:
> To be honest, the P function didn't completely break my blog. However, it did
> mess with several images on my site. Years ago, when I first started with
> WordPress, I used the "one-click installer" my web host provided. It set my
> directory as www.mydomain.com/Wordpress ... so every image I uploaded in the 2
> years I was there was stored as www.mydomain.com/Wordpress/wp-content/... I've
> gone back through and changed them (it was a bad naming schema to begin with),
> but that's not really the point. The point is that we have an inconsistent
> development process:
> - A trivial feature built by a member of the community-at-large is identified as
> such and rejected.
> - A trivial feature built by a core team member is included and requests to
> remove the feature are dismissed by the core developers.
More information about the wp-hackers