Right now we have a $content variable in node files. The designers/themers like to use the field specific variables and place them where they want them.

This often happens by calling $node->content['field_FOO']['#XXX'];

Let's add either $field_fieldname variables to the tpl files or something like $field->fieldname to the tpl files. These should be on anything where fields are attached.

Comments

yched’s picture

yched commented

We're already there. In CCK D6 *and* field.module D7, themers can use the $FIELD_NAME_rendered variables.

So I'm not sure what is missing :-)

mfer’s picture

mfer commented
Issue tags: +Needs documentation

Thanks. But, the designer/themers were not aware of this. There has been talk among a lot of them (dozens of the most active) who did not know about this.

It might be good to get this documented. Or, is it already documented?

yched’s picture

yched commented

The CCK 'advanced help' pages have an extensive 'Theming' section where this is documented.
CCK's README.txt encourages users to download advanced_help.module, as well as a few messages in the UI.

mfer’s picture

mfer commented

I'm going to leave this task open as a documentation issue. I would like the designers/themers to come up with other places they would like this documented so we can get them using this feature.

emmajane’s picture

emmajane commented
Status: Active » Fixed

As yched has mentioned, there is already documentation for this issue. Please see: http://drupal.org/node/62462

mfer, please encourage themers to contribute any additional information to these pages. Anyone with a d.o account can edit that content!

I'm marking this issue as fixed.

Status: Fixed » Closed (fixed)
Issue tags: -Needs documentation, -Needs design review

Automatically closed -- issue fixed for 2 weeks with no activity.

Issue tags: +Needs documentation, +Needs design review

Restoring issue tags, see #2125755: System messages removed all issue tags during D7 upgrade.