When editing a message type after having added an entity reference field of type content, all the site's content fields tokens will become available, even if I selected a specific bundle (node type) in the entity reference field settings.
If your site is complicated (lots of content types and fields) the edit page will become unusable (cause of token module and jquery I think). Even switching the Field language select list will freeze the page (for more than 10 seconds for me!).
If I remove reference fields, of course everything works nice and fast..
Adding more message types will also make the edit page slow (already during creation!), because all other message type fields' tokens will be available!
Is this intended functionality? In that case, why?
Comment | File | Size | Author |
---|---|---|---|
#7 | message-2381949-7-Tokens-make-form-unusable-.patch | 779 bytes | geek-merlin |
|
Comments
Comment #1
kopeboy CreditAttribution: kopeboy commentedComment #2
kopeboy CreditAttribution: kopeboy commentedComment #3
joep.hendrix CreditAttribution: joep.hendrix at CompuBase Internet Solutions commentedSame problem here.
In an Open Atrium solution a space content type has lots of extra fields with a lot of entity reference fields.
Editing the message types is impossible, no response due to the huge amount of tokens.
Comment #4
joep.hendrix CreditAttribution: joep.hendrix at CompuBase Internet Solutions commentedComment #5
joep.hendrix CreditAttribution: joep.hendrix at CompuBase Internet Solutions commentedComment #6
joep.hendrix CreditAttribution: joep.hendrix at CompuBase Internet Solutions commentedAs a work around I have installed https://www.drupal.org/project/token_tweaks.
Now the maximum depth of the token can be set in order to prevent the load of zillion tokens.
Probably the problem is caused by entity token?
Related issue: https://www.drupal.org/node/1058912
Comment #7
geek-merlinConfiming: This is a real PITA which makes the form unusable on any big site.
Fortunately it has a trivial mitigation.
Patch flying in.
Comment #8
Jorrit CreditAttribution: Jorrit at nCode for DOM Digital Online Media GmbH commentedPatch 7 is a good work around. It does not help users that want to select a token but it makes the page accessible.
Comment #9
NWOM CreditAttribution: NWOM commentedhttps://www.drupal.org/project/fast_token_browser is a better workaround than #6 for this issue.
Comment #10
bluegeek9 CreditAttribution: bluegeek9 as a volunteer commented