I am not sure whether and where I should report this, but
my watchdog is logging the following warnings on node creation:

More than one module has defined the mod-small token
More than one module has defined the small token.
CommentFileSizeAuthor
#6 morethanonetoken.png66.24 KBskizzo

Comments

Bushidoman’s picture

Bushidoman commented

Subscribing.

I'm getting a similar message.

More than one module has defined the node-url token.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

@Bushidoman See #845250: Duplicate [node-url] token definition with token module

skizzo’s picture

skizzo commented

Re OP, I can't find any other reference to mod-small in my Drupal tree

# grep -H -r mod-small /var/www/drupal
/var/www/drupal/sites/all/modules/token/token.test:      'mod-small' => '07/04/1984 - 00:00',
dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

I can't in the entire contrib repository.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Postponed (maintainer needs more info)
skizzo’s picture

skizzo commented
StatusFileSize
new morethanonetoken.png66.24 KB

The warning is logged also at night, on a system without any active user, when Google Bot visits some nodes (please see attachment). Manually running cron does not trigger the warning. I tried disabling few recently installed modules, to no effect. The only way I could get rid of the warning is by restoring the 6.x-1.13 token subtree (was there any db update associated with the 1.14 release? Thank you)

abdulFarooqui’s picture

abdulFarooqui commented
Status: Fixed » Postponed (maintainer needs more info)

I am also getting same warning message in logs after the latest update to 6.x-1.14. In my case, the site-url is also expanding to 'default', I am not sure if these two issues are related.

Update: My issue was not related. I was running cron through drush. And if the email templates used site-url, then it expands to correct URL only if drush has the extra -l parameter (to specify the website domain name). Once I started using -l parameter, it worked well.

Fannon’s picture

Fannon commented

Got the same Error. It appears in

/admin_hover/js/node

subscribing.

vstmusic’s picture

vstmusic commented

I have a similar message when I visit a node in which there is a comment published.

The warning token message in dbdog : "More than one module has defined the comment-since token"

Strange ! there were no warning bewore the update of token (6.x-1.14)

joel.serino’s picture

joel.serino commented

Subscribing.

Ditto. No error until after update to token (6.x-1.14)

Sera’s picture

Sera commented

*subscribing*

I can confirm this with Token 6.x-1.14. I get the message: "More than one module has defined the node-url token."

I use Token (6.x.-1.4) with Automatic Nodetitles 6.x.-1.2 and FileField Paths 6.x.-1.4

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

@Sera: Your problem is with the Notifications module. See #845250: Duplicate [node-url] token definition with token module.

skizzo’s picture

skizzo commented

...the "mod-small token" warning seems gone after installing token 6.x-1.15

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

Double check admin/reports/status to see if you get a warning about the mod-small token.

skizzo’s picture

skizzo commented

no, I don't.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Postponed (maintainer needs more info) » Fixed

Ok then, going to mark as fixed then. :)

Status: Postponed (maintainer needs more info) » Closed (fixed)

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

donquixote’s picture

donquixote commented
Status: Closed (fixed) » Needs work

sub.
Just had this myself.
"More than one module has defined the node-url token."
And yes, it is notifications vs the updated token module.

Now, what about a more useful and specific warning message in case of token conflicts?
The message should tell us which modules define the respective token, in which file and which function.
(yes, the file is quite useful as well, if the same module is in more than just one place)

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Needs work » Fixed

If you're using 6.x-1.x-dev I believe this should already been provided on the status report page.

Status: Fixed » Closed (fixed)

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