Voting starts in March for the Drupal Association Board election.
Users have requested the ability to use Tokens for Amazon's ASIN field, most often for use with the Automatic Node Title module.
The following issues were opened requesting Automatic Node Title and Token support.
Alternative solutions to CCK tokens were presented in the above issues. In #392524, rfay requested to open a new issue for patches.
This issue is to provide a patch to implement CCK field tokens for the ASIN field. This eliminates the need to use the solutions presented in #392524 and #991994, which required placing PHP code within "automatic title generation" field or creating a custom module.
Detailed information on the new Token functionality can be found at http://drupal.org/node/595464#using-tokens
User testing and feedback on the latest provided patch in Drupal 6 is needed.
Though originally this issue attempted to tackle D6 and D7 tokens, this issue now only applies to D6. Patches provided for D7 in this issue are no longer valid due to a change in the Token API.
For CCK field Token support in D7, see
Original report by cristinawithout
Sorry I couldn't do this sooner. I finally got some free time today, so here's a patch that implements tokens in the same manner that other CCK fields do so Amazon fields can used used . Regarding the issue of it needing to know the number, I believe it's safe to use item 0 for two reasons: 1. Why would anyone expect it to use a different number? 2. Other CCK field types use this behavior, therefore, it shouldn't be unexpected.
Anyway, I'm a PHP developer who's now doing Drupal, so forgive me if there's anything wrong with this patch or how I've submitted it.