[theme-reviewers] Themes and Post Meta/Custom Fields

Chip Bennett chip at chipbennett.net
Thu Oct 21 16:11:34 UTC 2010


These are good guidelines.

I think the ones that we can certainly implement as consistent with existing
guidelines are #1 and #2.

Any suggestion for such an automated way to remove such post meta data? (Yet
*another* argument for a Theme deactivation/deletion hook.)

Chip

On Thu, Oct 21, 2010 at 11:05 AM, Gene Robinson <emhr at submersible.me> wrote:

> I'm ok with the idea of themes adding post meta if they:
> 1. document it's function and purpose in theme docs, read-me, and/or
> options/settings page.
> 2. prepend the post meta with the theme slug like identifier
> 3. offer an automated way to remove the post meta should the user desire
> removal or to reset it.
>
> -Gene
>
> On Oct 21, 2010, at 11:53 AM, Chip Bennett wrote:
>
> > I just ran into another one, thanks to a Theme that outputs all of a
> post's custom field keys/values as post meta data: apparently, some Themes
> are adding custom fields to posts.
> >
> > Should there be some guidance here? Specifically, should Themes be adding
> meta information/custom field keys/values to existing posts without user
> knowledge?
> >
> > In my case, one Theme added various default Thumbnail images as custom
> fields, and another Theme added a "superawesome" custom field key (with a
> value of "false").
> >
> > Chip
> > _______________________________________________
> > theme-reviewers mailing list
> > theme-reviewers at lists.wordpress.org
> > http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
> _______________________________________________
> 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/20101021/8735e267/attachment.htm>


More information about the theme-reviewers mailing list