Michael, <div><br></div><div>Thanks... that makes sense...</div><div><br></div><div>But a concern here. Isn't it possible that by supporting the legacy behavior so thoroughly that lots of modules may upgrade to 7 but not actually make themselves compatible with fields-in-core? They won't look broken initially because old and new sites are using the legacy body field.</div>
<div><br></div><div>Shai<br><br><div class="gmail_quote">On Fri, Jan 15, 2010 at 1:10 PM, Michael Prasuhn <span dir="ltr"><<a href="mailto:mike@mikeyp.net">mike@mikeyp.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
One reason is that many modules and places in Drupal are used to $node->body and removing that standard and using $node->field_FOO is fine if you know what you are doing, but otherwise it's a bit of a legacy practice.<br>
<br>
-Mike<br>
__________________<br>
<font color="#888888">Michael Prasuhn<br>
503.512.0822 office<br>
<a href="mailto:mike@mikeyp.net">mike@mikeyp.net</a><br>
<a href="http://mikeyp.net" target="_blank">http://mikeyp.net</a><br>
</font><div><div></div><div class="h5"><br>
On Jan 15, 2010, at 8:02 AM, Shai Gluskin wrote:<br>
<br>
> @Naheem,<br>
><br>
> That doesn't answer the question. We can use a fields-in-core field to create a body field that automatically gets created when you create a new content-type. Sensible default settings have nothing to do with it. So I still ask, "Why are we using the legacy body field for new content types in D7?"<br>
><br>
> While we are talking sensible defaults... the default for a body field in a new content type should be to use the "Long text" handler and NOT the "Long text with summary." The use-cases for "Long text with summary" are far fewer than for "Long text." And it can take years for people to actually grok "long text with summary" anyway :). Now that we've got fields-in-core, we should be defaulting on a new content-type body field to "long text".<br>
><br>
> Shai<br>
><br>
> On Fri, Jan 15, 2010 at 10:50 AM, Naheem Zaffar <<a href="mailto:naheemzaffar@gmail.com">naheemzaffar@gmail.com</a>> wrote:<br>
> 2010/1/15 Shai Gluskin <<a href="mailto:shai@content2zero.com">shai@content2zero.com</a>><br>
><br>
> But this is what I don't get: Why is the body field still there when you create a new content-type the body field is still there on the content-type edit screen.<br>
><br>
> usability - most people will expect a content type to be useable after creation.<br>
><br>
> Customisation is great, but it should never be at the expense of good defaults<br>
><br>
><br>
><br>
<br>
</div></div></blockquote></div><br></div>