If I enabled CCK Sign-up notifications in Notifications I get the following error on status page.
There are no errors when this component is not enabled 

Duplicate tokens The following tokens are defined by multiple modules and may cause problems when performing token replacement. 
node:node-url (defined by modules: token, notifications_cck_signup) 
node:node-teaser (defined by modules: notifications_cck_signup, notifications_content) 
node:node-body (defined by modules: notifications_cck_signup, notifications_content) 
node:node-teaser-raw (defined by modules: notifications_cck_signup, notifications_content) 
node:node-body-raw (defined by modules: notifications_cck_signup, notifications_content)

Using Notifications 6.4-Beta7
if this is a Notificaitons module issue please let me know

Comments

allan1015’s picture

allan1015 commented

Some research around duplicate tokens

Getting duplicate errors on these tokens:
node-teaser, node-body, node-url, node-teaser-raw, node-body-raw

So I removed assignment of these tokens, sorta brute force
In notifications_cck_signup.module

Comment out these lines:

// $tokens['node']['node-teaser'] = t('The node teaser.');
// $tokens['node']['node-body'] = t('The node body.');
// $tokens['node']['node-url'] = t('The node view url for read more links.');
// $tokens['node']['node-teaser-raw'] = t('Unfiltered node teaser. WARNING - raw user input.');
// $tokens['node']['node-body-raw']

// $values['node-teaser'] = !empty($node->teaser) ? check_markup($node->teaser, $node->format, FALSE) : '';
// $values['node-body'] = !empty($node->body) ? check_markup($node->body, $node->format, FALSE) : '';
// $values['node-url'] = url('node/'. $node->nid, array('absolute' => TR//UE));
// $values['node-teaser-raw'] = !empty($node->teaser) ? $node->teaser : '';
// $values['node-body-raw'] = !empty($node->body) ? $node->body : '';

There should be some namespace or other way do avoid this, no idea what is right thing to do

jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
commented
Status: Active » Closed (duplicate)

Marking this as a duplicate of #1002770: Notifications 4.x compatibility, as I suspect it is due to the fact that the CCK Signup notifications module implements the 3.x notifications API.

g4’s picture

g4 commented
Component: Code » CCK Signup core

I also got this error and a bit of newbie.
Does it need to be resolved or can I ignore them? If I ignore them, what could potentially go wrong?

lhubbert’s picture

lhubbert commented

I ignored it and my regular content notifications went out with "Array" written where I had replacement patterns. Haven't figured out a solution but need to in the next week or so and will post back if I figure it out. Take away - if you're using token replacements for other notifications do not ignore.

bsandor’s picture

bsandor commented

I am in the same situation:

Notifications 4, Duplicate Tokens.

Is there any quick solution? Besides this needs to be fixed.

bsandor’s picture

bsandor commented

I also found this link: http://peterpetrik.com/blog/more-one-module-has-defined-node-url-token