Expose the node title and body as independent panels "content types"

I bit more thoughts... if we look at how this is approached in views, it is views who exposes the node core fields itself. So, aside from needing to show the title and body fields as separate content types in panels, maybe it is also needed to do the same for other node core fields in the node, such as the author, created date, etc.

So... it seems it would make more sense if it was Panels who exposes these fields as independent Panels "content types"?

So I guess it should be implemented by ctools, in the directory ctools/plugins/content_types/node_context, as a separate file named node_fields.inc? And here we can start exposing the node title, body, created, changed and node author (with an option to link to the user profile).

Sounds good? Or do you already have plans for this? I have a bare idea on how to do it, but I may try to, if that helps.

Here's one doubt:

The label for the title and body fields can be changed in the node type settings screen. Also, when the body label is left blank, then the body for that node type is not used.

Question: should we expose title and body for each node type as separate entities?

If yes, the label for these couple of entities exposed to Panels ought to be something like "@user-defined-label in @node-type"?

If no, should the label for these entities by simply "Title" and "Body"? (I don't like this)

If both, then what? :-/

Another doubt: what about the icons? May we start with 'icon_node.png' for all these elements?

BTW, I think this is ctools business.

More thoughts on #6 about title/body:

It looks like we could expose just one title/body, and just let the admin provide a label. This would be similar behavior in views. However, in views you can add the title several times, each related to a relationship that points to a different node type, and you can label each "title" field according to the node type the field refers to. I'm not sure if this is possible in Panels.

Maybe like this? The title/body settings form, may ask if you want to relate this field to a particular node type, or just any. That way you can add title/body several times to a panel, each related to a node type, while the title/body fields are just exposed to panels once. You can choose which node type or any in the settings form. Sounds good?

Ok, here's an attached file that implements title, body, created and updated fields.

The file is aimed to be copied to ctools/plugins/content_types/node_context, and it should be renamed to node_fields.inc.

It's a start. Please, critique. :) Once this is in the right direction, we can add more fields, such as the node author, and may be that's enough for now.

Ah, just for reference. Latest development snapshots of CCK contain a reviewed implementation of the CCK fields integration, and also support for field groups, which is being enhanced here: #495582: Panels integration for multigroups

File node_fields.inc updated. This one also implements node author and published status.

AFAICT, I'm done adding node fields here. Is it ok like this, or should I change anything? Do you want me to add any other field? :-|

...or do you want separate content types as suggested in #5? I think I forgot and did it using subtypes, using the same approach as in CCK.

Once this is in, I may eventually try to do something similar for a couple of user fields: nickname and date registered / member for.

Here's a first try for an individual node field template. Implements the node title. Please, let me know if it's ok.

Updated to fix PHP issue. Sorry.

hmm... true.

Here's an updated copy. Here I'm using:

  // Get a shortcut to the node.
  $node = &$context->data;

..by reference, so PHP does not need to copy the object data.

If this is ok, then I'll prepare more fields as standalone content types.

Sorry for the doubts, but I like to be sure.

BTW, the other content type use this:

$node = isset($context->data) ? drupal_clone($context->data) : NULL;

where if there's no node, then something like $node->nid will fail. This might be something for a separate patch maybe?

Ok, feel free to commit this one without the reference. Then leave this as "needs work", then I'll update when I have the other content types using the same exact pattern as you commit.

That way, I just don't need to update the node title again.

Oops! It seems the changelog was updated, but the new file was not added.

http://drupal.org/cvs?commit=238852

Reminder: the missing file is the one in #18 without the & to get the node by ref.

I'll post a few more content types for node fields later today.

Well, I'm attaching a patch this time.

It includes the following content types:

- node_title
- node_body
- node_author
- node_created
- node_updated

So you can dismiss the files attached before. This patch contains everything, just following the same pattern as discussed.

There may be minor fixes that you may wish to apply, so please let me know if you wish me to make any other change.

I would swear that the body was working when I tested, but now it's broken because it doesn't provide a settings form, an empty function seems to be enough.

In case it's not easy to fix this requirement elsewhere, attached patch fixes it here.

Hey, you're welcome! ...also, thanks as well for your hard work in these monster modules! :)