I have set up a store using the CCK and views exports provided. Everything working nicely. Have made various adjustments to tpl files to customize the store item detail pages i.e. amazon_store/item/xxxx

The one thing I'd love to include would be one or more of my custom cck fields on the amazon store item detail page. Specifically I'd love a commentary field where we say a few words about each item to appear above all the information which is pulled from Amazon.

I'm not knowledgeable enough to get the additional fields which appear on my cck content type node pages to display via amazon_item_detail.tpl.php

I'm not really sure if this is simple or difficult thing. Any thoughts appreciated.

Comments

vtsaran’s picture

+1 to the suggestion above. This is the only thing that keeps me using Amazon native widgets. Is it programmatically possible to insert our own descriptions or annotations to the displayed items? This does not have to be sent back to Amazon, so this is just a change in the local database.

Thoughts?
V

rfay’s picture

Your node in a CCK content type is a separate thing, but you could easily find it with a query using the ASIN (which is available in the amazon_item_detail.tpl.php).

Something along the lines of

1. A query on content_type_xxx searching for the ASIN - get the node, perhaps.
2. Either operate on that data, or do a node_load() and then operate on the date you get.
3. Add the information as you see fit.

So the essence of this is using the information you have in the amazon_item_detail.tpl.php (which is the ASIN) to get your node, so you can add information as you will.

I hope that's not too obscure an answer. Let me know if I can help out. Next time I work on the module perhaps I'll roll out an example.

Either of you are welcome to add to the documentation on how to do the theming, since you're getting to be experts!
http://drupal.org/node/494402

rfay’s picture

Status: Active » Fixed

Marking this as fixed. If you need more help, please reopen. Also, don't hesitate to improve the documentation.

Status: Fixed » Closed (fixed)

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