[theme-reviewers] Question about ob_start and ob_get_clean (Vicky Arulsingam)

Darren Slatten darrenslatten at gmail.com
Sun Jul 3 00:22:50 UTC 2011

My solution provides *additional functionality* to compensate for
poorly-written or outdated plugins and instances where WP core falls short.
It amazes me that I have to defend it at all. Even more amazing is the fact
that the alternatives being proposed are:

   1. Settle for sub-optimal HTML output.
   2. Contact all plugin authors and tell them to change their plugins to
   suit my personal tastes (and ignore sub-optimal code caused by WP core).
   3. Tell my theme users to contact the authors of the plugins they

I mean...seriously?

On Sat, Jul 2, 2011 at 5:27 PM, scribu <mail at scribu.net> wrote:

> On Sun, Jul 3, 2011 at 1:18 AM, Darren Slatten <darrenslatten at gmail.com>wrote:
>> *How do you ensure that this doesn't mess up plugin functionality when
>>> you're wrong about the necessity of the code a plugin is using? *
>> Keep in mind that the theme doesn't actually change anything by default;
>> it merely enables the user to make changes. Therefore, this question
>> would have to be answered on a case-by-case basis by users who have
>> opted to take advantage of the functionality provided by the theme.
> So, instead of merely doing it wrong yourself, you're encouraging users to
> do it wrong. Nice.
> --
> http://scribu.net
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20110702/5109ef32/attachment.htm>

More information about the theme-reviewers mailing list