I have just started using the Fusion theme and have a question regarding placement of CCK Content Type data in the theme.

Currently I have developed a custom theme based on the Fusion core. Main PAGE header images are placed in the CONTENT TOP region via blocks that contain the image.

I have also developed a number of custom CCK content types and - for a couple of them - would like to be able to specify (and upload) a page header image and have it placed automatically in the CONTENT TOP region of the node. The remainder of the information in the content type should be placed where it normally is in the CONTENT region of the node.

Is this possible? If so - could someone give me a tip on how to do this?

Thanks . . . Mike

Comments

jeremycaldwell’s picture

jeremycaldwell commented
Status: Active » Fixed

Hi Mike, normally to get an image that is uploaded to a node through a CCK field to display in the content top region you would create the CCK field as an image field. Then through that content type's settings set it to hidden from display.

Then you create a View to display one CCK image field you created and set it's argument to check by node ID. Also set it to filter by "published" and "content type" (whatever content type you are using to create the nodes with images) and create the View as a block. Then place the block to appear on the pages you want it to appear on and in the content top region. If done correctly it will then use the View to display the CCK field from the node thanks to the argument for the node ID.

Another method is to create a node.tpl.php for the content type you are editing. The naming convention is node-CONTENTTYPE.tpl.php. Where CONTENTTYPE is the machine name of your content type. And this node-CONTENTTYPE.tpl.php is a clone of your existing node.tpl.php. Once you have that in place you can manually print or hide the CCK fields anywhere you want in your custom node tpl file.

More information about that can be found here: http://drupal.org/node/282225

And lots of other places through a search on Google. Hope that helps!

Status: Fixed » Closed (fixed)

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