Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hallo,
i have a problem with this module. When i turn it on, i cant use it in taxonomy term autocomplete field. When i does it is not only showing nothing, but also it not allowed submit a node with it on apple OS X.
Comment | File | Size | Author |
---|---|---|---|
#21 | interdiff.txt | 1.04 KB | purushotam.rai |
#21 | field_default_token-taxonomy_terms-2194803-21.patch | 7.19 KB | purushotam.rai |
#16 | field_default_token-taxonomy_terms-2194803.patch | 7.23 KB | maximkashuba |
Comments
Comment #1
maximpodorov CreditAttribution: maximpodorov commentedDo you mean any taxonomy term reference field with autocomplete widget creates a problem?
Comment #2
kryber CreditAttribution: kryber commentedYes! When i am using the FDT there, it is not working. When i press submit and come back, its not there. But when i am using it in text field, it is.
Comment #3
maximpodorov CreditAttribution: maximpodorov commentedOK, I understand. Will fix this.
Comment #4
kryber CreditAttribution: kryber commentedThank you. Really looking forward. And i also noticed, that when i am using it like this (with taxonomy term reference field), it gave me an error on apple devices when i submit a node with taxonomy term reference using Field default token. After i press submit, on apple os x it goes to the redirected error page. Just on Apple os x. On Windows the node submision went ok.
Comment #5
Ivan Simonov CreditAttribution: Ivan Simonov commentedConfirm it.
Default value token can not be saved for taxonomy term reference field with autocomplete widget.
Comment #6
Ivan Simonov CreditAttribution: Ivan Simonov commentedTaxonomy term reference field with dropdown list widget do not use saved default values too.
Comment #7
fyberoptik CreditAttribution: fyberoptik commentedVery interested to see this working :)
Comment #8
sarazil CreditAttribution: sarazil commentedI'm also having this issue. It refuses any non-vocabulary term as that's how the field is designed. Best solution would be for it to validate things after token swapping has occurred and to accept valid tokens as alternatives to vocabulary terms. (I'm running drupal on an ubuntu VM)
Comment #9
kopeboy CreditAttribution: kopeboy commentedI actually can't see the default value at all, neither using Select list nor Autocomplete.
Using mac os x and both chrome and safari (but I don't get why this should be relevant) and Display Suite module (Default one column layout) on the node add form page.
The problem is not only on the node/add form but also on the field/edit page. If I set the default token value and save the field, reopening field for editing already doesn't display the default value just saved.
I also tried to set both the source and target field setting to be limited to 1 value.
What I'm trying to do (I think this is the most common use case) is to load the same field value saved on another entity, referenced to the Current user with an Entity Reference field.
In my case for example:
[current-user:profile-spouse:field-my-wedding-link:field-wedding-location]
So, are Term Reference fields supported at all by this module?
Comment #10
carteriii CreditAttribution: carteriii commentedI believe the underlying problem may be with the widget and not simply with taxonomy terms specifically. I have an, "Autocomplete (Tags style)" widget in use to set an EntityReference field for a user entity but using either [current-user:uid] or [current-user:name] results in an error like:
. The field outline/border shows red with that in it, so I suspect it's the widget which causing the failure even with taxonomy terms.
Comment #11
ikeigenwijs CreditAttribution: ikeigenwijs commentedSame issue but with
entity reference fields.
auto complete widgets wants to validate the token instead of the replaced value of the token
"Researcher: found no valid user with that name."
Comment #12
nixar CreditAttribution: nixar commentedI'm having the same issue right with a Select widget. The DB query expects an integer value even after I checked the box to assign a taxonomy term name and not a term ID.
Comment #13
CD CreditAttribution: CD commentedAnyone come up with an answer?
Comment #14
internal CreditAttribution: internal as a volunteer commentedConfirmed here. It should be a critical bug that should be added to the project page. It seems it only works with nodes.
Comment #15
gdhp CreditAttribution: gdhp commentedIn reference to number #11 - same problem here.
Would be great if we can get a patch for this.
Comment #16
maximkashubaAdds support for the taxonomy term autocomplete widget
Comment #17
dmsmidtI fear multiple issues with taxonomy terms are overlapping here.
Let's focus in this issue on the autocomplete widget.
Setting to needs review.
Comment #18
jonnyeom CreditAttribution: jonnyeom as a volunteer commentedI am unable to use this module when using a user reference field (available with the references module) in the same manner as a taxonomy term. Has anyone else tried to use field_default_token this way?
Comment #19
dmsmidtHave you tried https://www.drupal.org/node/2790059#comment-11570429?
It aims to make this module more generic.
Comment #20
Donit CreditAttribution: Donit commented#16 doesn't work.
Comment #21
purushotam.rai CreditAttribution: purushotam.rai at QED42 commentedPatch #16 works for me, but I would recommend validating vocabulary_machine_name instead of vid.