Timeline for Services 3: Setting taxonomy terms on node creation/update
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 16, 2015 at 5:39 | comment | added | tyler.frankenstein |
And for multiple values using an autocomplete widget, you can send: "field_tags":{"und":"Foo,Bar"} - This works both for creating new terms and using existing ones.
|
|
| Mar 24, 2014 at 15:30 | comment | added | tyler.frankenstein |
In D7, a taxonomy term reference field with the autocomplete widget uses JSON like this: "field_tags":{"und":"Foo"}" When it is an autocomplete, the term name needs to be used instead of the term id.
|
|
| Oct 29, 2012 at 12:45 | comment | added | khex | "this" - it was a russian keyboard layout | |
| Oct 29, 2012 at 10:48 | comment | added | avpaderno♦ | What does ершы in "you doesn't need to create ершы sequence" mean? | |
| Oct 27, 2012 at 16:40 | comment | added | khex |
But this "field_taxonomy": { "und": [ 11 ] } doesn't work at all in my case drupal.stackexchange.com/q/47589/10671
|
|
| Oct 23, 2012 at 13:51 | comment | added | jbaiter |
I'm not using autocomplete, but checkboxes for the vocabulary items. After a few hours of trial and error and a few glances at the Services source code, I was able to POST my vocabulary items in the following format: "field_taxonomy": { "und": [ 11 ] }
|
|
| Oct 22, 2012 at 22:34 | history | answered | khex | CC BY-SA 3.0 |