<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
andrew morton wrote:
<blockquote
cite="mid:fab053ce0909160719o34d3b61dv5ecc23806d13576@mail.gmail.com"
type="cite">
<pre wrap="">On Wed, Sep 16, 2009 at 10:03 AM, Nancy Wichmann <a class="moz-txt-link-rfc2396E" href="mailto:nan_wich@bellsouth.net"><nan_wich@bellsouth.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">After reading Eaton's well-written article
<a class="moz-txt-link-freetext" href="http://www.lullabot.com/articles/great-pretender-making-your-data-act-field">http://www.lullabot.com/articles/great-pretender-making-your-data-act-field</a>,
I tried this in a module I work on. The fields are definitely showing on
"Manage fields" in CCK.
However, those added fields do not seem to be available to Views. One of the
reasons why I am really interested in making this change is so that
something like Node Export can see these fields automatically. What more
needs to be done to the suggested code to have CCK reflect these fields to
other modules?
</pre>
</blockquote>
<pre wrap=""><!---->
All that hook_content_extra_fields() really does is tell CCK about
other node data so that they can be reweighted using the UI. Views
support is a whole different animal that's done through
hook_views_data()... and thorough documentation would make a great
book.
andrew
</pre>
</blockquote>
You can find some documentation on Views2, including
hook_views_data(), here: <a
href="http://views-help.doc.logrus.com/help/views/api">http://views-help.doc.logrus.com/help/views/api</a><a
href="http://views-help.doc.logrus.com/help/views/api-tables"></a><br>
<br>
Seth<br>
<br>
</body>
</html>