Closed (works as designed)
Project:
Web service client
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
27 Sep 2011 at 19:49 UTC
Updated:
29 Jun 2014 at 14:11 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
klausiInteresting, I do not see this message on my status report page. I greped through the entity and token module, but could not find it. How can I reproduce that message?
Anyway, web service descriptions are configuration items. Is there any use case why we would want to expose tokens at all? We could just set 'token type' to FALSE in hook_entity_info().
Comment #2
wesnick commentedSetting to FALSE did not work, but unset did.
Comment #3
klausiStrange. Again: How can I reproduce that error message? On what page exactly? What module throws the message? What is the exact message?
Comment #4
wesnick commentedI can figure out how to reproduce it in a clean install. My installation is producing an extra token output, somehow it is producing a token, without a corresponding type
For what it's worth, screenshot attached
Comment #5
klausiThanks, does this patch fix the issue for you? Make sure to clear the cache.
Comment #6
wesnick commentedNo, this patch doesn't fix it. I have been able to reproduce this on a vanilla install. The offending module that is adding tokens is token.tokens.inc in this code block around line 40.
Entity token module filters wsclient_service token types, but token module adds in tokens automatically for all entities that have one of the above conditions. If you have the wsclient_ui module installed, the following is true
and token module adds wsclient uri token.
So either, we explicitly unset $entity_info['token types'], or we provide some property info for wsclient_service, but as you said, there is probably no real use case for this.
Comment #6.0
wesnick commentedfixed grammar
Comment #7
klausiI assume this is not an issue anymore? Reopen if this is till a problem.