How to theme CCK field with a content-field-my_field.tpl.php file

I'm having the same question...even the default field.tpl.php is not working

From D6, no specific CCK instructions are needed; overriding the template is now done just like for any other module : find the template file that interests you, copy it into your theme's folder, override the file to suit your needs, rebuild your cache registry, et voila.
In your case, the file is in cck's 'theme' folder (which makes us assume it's rather easy to spot, this will probably become a sort of convention for 'large' module anyway).

Be sure to check devel's devel_themer.module whenever you're having troubles figuring out what to override

it seems to be related to the 'path' set in hook_theme() of the content.module?
it looks like now it uses cck/theme/field.tpl.php instead of the php in theme/mytheme/field.tpl.php

Please make sure you're using latest CCK 6.x-2.x. I committed a fix for this a few days ago.

"I saw that there is a field.tpl.php and a content-field.tpl.php files under the theme folder of CCK module."

No, there is only a content-field.tpl.php file. The other one is a leftover from a previous CCK D6 state (the file was renamed from field.tpl.php to content-field.tpl.php), which is still there probably because you copied the new /cck folder over the old one instead of deleting the old one.

This being said, I can't seem to get a field-specific template to be used either. I'm afraid this is related to the 'formatters as theme' refactoring, where the actual call to theme() is left to drupal_render($element = array('#type' => 'content-field', ...)). I could have sworn I tested per-field templates since this got in, though...
Investigating.

Your feeling is right. This will work of course, but is only a workaround, not inline with drupal theming principles.

Reintroduced the search for variant template files, and added a cck/theme/README.txt file

Forgot to add : in addition to content-field-[FIELD_NAME].tpl.php, we now support the content-field-[CONTENT_TYPE].tpl.php and content-field-[FIELD_NAME]-[CONTENT_TYPE].tpl.php patterns.

Anyone trying to do this should be aware that it may not work correctly in Drupal 6.2. There is a core bug at #241570: Theme preprocess functions do not get retained when using patterns that is fixed in Drupal 6-dev and will be fixed in Drupal 6.3 when it is released. The bug is that the preprocessor doesn't get triggered so the values you get in the template may not be right.

I'm experiencing the bug with content-field.tpl.php, in Drupal 6.3.

Was this fixed in that last release or is a patch required?

Cheers

No Patch required
Use CCK RC4
Drupal 6.3

Make sure that content-field.tpl.php [base template]
is in your theme folder
as well as
content-field-field_myfield.tpl.php

Regards
Alan

hi ...could someone update the Theming CCK Input Form Handbook. for D6. I'm getting a bit and pieces here and not so clear either :-)

I'm trying to organize my own notes for this-- here's what I have - I'm not sure how to edit drupal handbooks.

Theme Individual CCK 2 Fields

• copy content-field.tpl.php from sites/all/modules/cck/theme to your theme folder
  (thanks alanburke: http://drupal.org/node/269319)
• make your template: content-field-field_name_of_my_field.tpl.php -- placed in your theme folder (or other file names, see theme info output from devel module or complete list of new templates (note: i usually just put gobbledy gook html in an empty file - just to get the template to show up something besides default output. Later, I go back and really edit the theme output for the fields with the correct syntax. You don't need to clear the cache after you get your tpl.php registered (again, unless you move/rename it)
• add your new template files to your theme folder - you can nest these in folders, just keep in mind you need to clear your cache to get the templates to show up if you move them around
• clear theme registry cache manually, or visit admin/build/modules to trigger a rebuild, or execute drupal_rebuild_theme_registry(); to register your new template files

chachasikes thanks for this! really helped me out.

Thanks!

Subscribing!!

I've spent a couple of weeks looking for what was in this thread and this one. Damn, it's not so much knowing what's wrong, it's knowing how to ask the question in the right way.

Subscribing.

Subscribing.

This is very good and it works. [#20]
Now, the same, for the edit page?

How can we do that?

thank you

If you want to theme a field in Drupal 6 and you are developing your own module, you can do the following:

Add your module to the theme registry for 'content_field'.

By using array_unshift, which adds an item to the beginning of an array, you can place your custom module first in line for the content_field templates.

function mycustommodule_theme_registry_alter(&$theme_registry) {


	$thisPath = drupal_get_path('module', 'mycustommodule');
	array_unshift($theme_registry['content_field']['theme paths'],$thisPath);
}

You could then put your own content-field.tpl.php in your module folder, or, as was more useful to me, you can create a field template for just the content type you're working with in your custom module, content-field-mycustomcontenttype.tpl.php. You then have to clear the theme registry, and voia! You can now edit the HTML hidden inside the $content variable in your node template. And also the template sits in your custom module instead of your theme folder. I try to avoid adding more templates to my theme folder, because it keeps all the files for your custom module together, and it keeps your theme folder and template.php file in your theme folder from getting weighed down with hundreds of files. This sort of organization is really helpful, if you are working on a large drupal site with lots of custom modules.

This didn't work for me. The module path shows in the 'theme - paths' at index 0, but the default cck template is still being used.

I realize this is old, but here goes anyway. Make sure your tpl file is called content-field-field_name_of_field.tpl.php. Note the two "field"s in there. Also note the dashes and underscores. The simplest way to get this right is to go to the Manage fields tab and copy your field name from there. This will be field_name_of_field. Then put a dash in front of that and add it to the content-field template file.

If you're using a sub-theme, like with Zen, you'll also need to copy content-field.tpl.php into your theme directory. I couldn't get content-field-field_image.tpl.php to work in my theme until I copied content-field.tpl.php in as well.

Just wanted to say I've made a video tutorial about theming CCK fields in Drupal 6.

@drupal librarian - Thanks for the video.

#15 and #18 worked for me.

I now have the following in my theme directory, and a field called field_artistwebsite in my content type.
content-field.tpl.php
content-field-field_artistwebsite.tpl.php

I was able to re-write the output of a CCK Link field so that it removes the "http://" on the display title on the node.

I did this by adding the following lines of code in replace of the commented out print statement below:

          <?php $item['display_title'] = str_replace("http://","",$item['display_title']);
          echo "<a href=\"".$item['url']."\">".$item['display_title']."</a>";
          
          /* Commented out original PHP print statement
           * <?php print $item['view'] ?>
           *
           */
          ?>

Subscribing.

I was having problems getting this to work until I disabled and uninstalled the Contemplate Module and Display Suite. I guess one of them was intercepting the theme.

Comment #20 worked for me. I had a CCK field called field_amazon, so I created a template file called content-field-field_amazon.tpl.php, which I stored in a directory called templates in my theme directory.

Once it was working, I could make changes to the template, upload them, and have the changes appear on refreshing the node. I did not need to clear the cache each time.

I was hoping that Contemplate would let me do this via a module, but it requires you to them the entire node, and it doesn't take the CCK Display Fields settings into account. And Display Suite seemed to le you do this (and much much more) to Views, not nodes.

1 Jul 2012 Note: This suddenly stopped working for me. I was able to re-enable it by (a) ensuring that my theme root had a copy of content-field.tpl.php (copied from all\modules\cck\theme), and I moved my own template file out of my templates directory, and also into my theme root.

@iantresman Thx for that last tip. Had trouble with this until we also copied over content-field.tpl.php to our theme folder.