Timeline for unlimited number of values gets really big
Current License: CC BY-SA 3.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 8, 2016 at 9:08 | history | edited | avpaderno♦ |
edited tags
|
|
Oct 19, 2014 at 1:25 | history | tweeted | twitter.com/#!/StackDrupal/status/523646037836460032 | ||
Oct 16, 2014 at 15:49 | comment | added | Alfred Armstrong | As per @j-reynold's answer below, you should definitely have the inhabitant and city as separate entities. A multi-valued field attached to the node will lead to all sorts of problems, as you have discovered. | |
Oct 16, 2014 at 15:34 | comment | added | Thanos Darkadakis | field type is text | |
Oct 16, 2014 at 15:14 | answer | added | J. Reynolds | timeline score: 3 | |
Oct 16, 2014 at 15:12 | comment | added | Alfred Armstrong | What's the field type? Entity reference? You should be able to configure it to use autocomplete. | |
Oct 16, 2014 at 14:59 | review | First posts | |||
Oct 16, 2014 at 15:10 | |||||
Oct 16, 2014 at 14:56 | history | asked | Thanos Darkadakis | CC BY-SA 3.0 |