I think "enclosure" is valid? It only exists on the Embedded Media Tests post, which *does* have enclosures.<div><br></div><div>Chip<br><br><div class="gmail_quote">On Thu, Oct 21, 2010 at 11:37 AM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com">edward.caissie@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Umm ... aside from a few other issues related to the Test Data that appears to coming up at the moment, included with the Test Data are five (5!) custom field keys:<br>
<br><ul><li>email_notification</li><li>enclosure</li><li>
geo_public (set to 0)<br></li><li>jabber_published</li><li>superawesome (set to false - twice!)</li></ul>So, anyone else want to refresh their database and do a fresh import of the test data?<br><br>Look for the above custom field keys ... and issues with the imported data throwing notices on Twenty Ten, too!<br>
<br><br>Cais<br><br>PS: Use the following simplified method:<br>1) Go into phpMyAdmin ... drop the database.<br><span style="font-weight:normal"></span><span style="font-weight:bold;color:rgb(32, 74, 135)"> </span>2) Go to site ... re-install (using same database just dropped)<br>
<span style="font-weight:normal"></span><span style="font-weight:bold;color:rgb(32, 74, 135)"> </span>3) Go to the Test Unit Data; download.<br><span style="font-weight:normal"></span><span style="font-weight:bold;color:rgb(32, 74, 135)"> </span>4) Import (importer works without re-activating?!)<br>
<span style="font-weight:normal"></span><span style="font-weight:bold;color:rgb(32, 74, 135)"> </span>5) Edit the "Layout" test post ... <br>EAC<div><div></div><div class="h5"><br><br><br><div class="gmail_quote">
On Thu, Oct 21, 2010 at 12:27 PM, Gene Robinson <span dir="ltr"><<a href="mailto:emhr@submersible.me" target="_blank">emhr@submersible.me</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex"><div style="word-wrap:break-word">I think #3 would be best accomplished via a Theme's settings/options page. Even if a deactivation hook existed, I don't think i would want it to reset all of a themes options and custom settings without user consent. <div>
<br></div><div>To some degree users who change themes and plugins often will always have cluttered options and postmeta. At least if the functionality and intention is well documented and the option is there to reset or delete settings when the theme is active, users who don't want to muck about with the database are empowered.</div>
<div><br></div><font color="#888888"><div>-Gene</div></font><div><div></div><div><div><div><br><div><div>On Oct 21, 2010, at 12:11 PM, Chip Bennett wrote:</div><br><blockquote type="cite">These are good guidelines.<br>
<div><br></div><div>I think the ones that we can certainly implement as consistent with existing guidelines are #1 and #2.<br><div><br></div><div>Any suggestion for such an automated way to remove such post meta data? (Yet *another* argument for a Theme deactivation/deletion hook.)</div>
<div><br></div><div>Chip</div><div><br></div><div class="gmail_quote">On Thu, Oct 21, 2010 at 11:05 AM, Gene Robinson <span dir="ltr"><<a href="mailto:emhr@submersible.me" target="_blank">emhr@submersible.me</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
I'm ok with the idea of themes adding post meta if they:<br>
1. document it's function and purpose in theme docs, read-me, and/or options/settings page.<br>
2. prepend the post meta with the theme slug like identifier<br>
3. offer an automated way to remove the post meta should the user desire removal or to reset it.<br>
<font color="#888888"><br>
-Gene<br>
</font><div><div></div><div><br>
On Oct 21, 2010, at 11:53 AM, Chip Bennett wrote:<br>
<br>
> 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.<br>
><br>
> Should there be some guidance here? Specifically, should Themes be adding meta information/custom field keys/values to existing posts without user knowledge?<br>
><br>
> 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").<br>
><br>
> Chip<br>
</div></div><div><div></div><div>> _______________________________________________<br>
> theme-reviewers mailing list<br>
> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
> <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</div></div></blockquote></div><br></div>
_______________________________________________<br>theme-reviewers mailing list<br><a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br><a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</blockquote></div><br></div></div></div></div></div><br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br>
</div></div><br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>