URL alias, tokens is replacing 0s and 1s with node and entity Has anyone seen a case that url aliases or tokens end up replacing certain numbers in a url with the words node and entity. A UTC Timestamp in my url ended up replaced like this:

node4328522entityentity


I cannot find any errors in the watchdog table. It seems like it's trying to "encode" numbers, but those are numbers that shouldn't be encoded. Or another possiblitiy I've thought of is maybe it is trying to grab something out of a non-existent array at index 0 and 1?
This seems pretty similar to what is asked in the question about Tokens causing incorrect text substitutions .

Refer to my answer in that question for various options to further debug what might be going on. If you can, please enhance your question (by editing it) to indicate which of the possible reasons in your case do apply, or don't apply at all.

Also note the brand new comment there (from "diego"), 
here is what that comment says:


  I was able to find a work around at east for the Webform submissions. If I use a Rule to send the email (using [data:{field-name}-display] tokens) instead of the Webforms built in email function it doesn't seem to substitute any of the tokens.