[theme-reviewers] Guidance on theme security
chip at chipbennett.net
Wed Oct 20 14:02:34 UTC 2010
Perhaps we should indicate an allowable age of backward-compatibility
support? What's the right answer here?
1) Themes must support current major WP version only (e.g. 3.0, not 2.9.x)
2) Themes may support a certain number of previous major WP versions (e.g.
for 3.0, Themes may provide backward-compatibility for 2.9.x, or 2.8.x)
3) Themes may provide backward-compatibility as old as the Developer wishes
I think One might be a bit restrictive, and difficult to enforce (WP 3.0
adoption is at just over 49%, 4 months after release), but certainly easiest
on the Review Team. I think Three would be way too difficult to manage, and
would end up causing nightmares for the automated checks (Theme Check and
the Uploader Script), due to backward-compatibility support for deprecated
functions. So, it would seem to me that Two is the most viable option.
The question is: how far back?
On Wed, Oct 20, 2010 at 8:28 AM, Gene Robinson <emhr at submersible.me> wrote:
> A quick draft item has been added to the Theme Review ...
> Looks good. I think it would be a service to theme developers to state
> that bloginfo('url') is a wrapper for home('url') that provides backward
> compatibility for versions < 3.0 Although an opposing argument might view
> this as enabling people to hold out on upgrading WP.
> @Nacin - When you review Simply Works Core 1.3.3<http://themes.trac.wordpress.org/ticket/1596> ,
> I'd appreciate your going-over my <http://themes.trac.wordpress.org/ticket/1566>previous
> review's suggestions <http://themes.trac.wordpress.org/ticket/1566>.
> -Gene (emhr)
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the theme-reviewers