Timeline for How to hand over value of field 1 to class array of field 2 programmatically in .theme
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 21, 2016 at 18:14 | vote | accept | nilsun | ||
| Apr 10, 2016 at 15:23 | answer | added | 4uk4 | timeline score: 1 | |
| Apr 10, 2016 at 10:04 | history | tweeted | twitter.com/StackDrupal/status/719103743065767936 | ||
| Apr 10, 2016 at 10:00 | history | edited | nilsun | CC BY-SA 3.0 | added 103 characters in body; edited title |
| Apr 10, 2016 at 9:56 | comment | added | nilsun | Maybe this is rather a feature discussion on Drupal.org, not sure. And probably theming level is not the right place for that functionality. It is arguable if this handing over of field values to theme classes should happen on theme or module level. But it is not arguable that this functionality would be the only exceptable reason for the whole HTML container mass in Drupals theme output. Otherwise we have no flexibilty in the choice of HTML/CSS whatever frameworks or boilerplates. There should be an obvious way to hand over such values to change the classes of markup in the same context. | |
| Apr 10, 2016 at 9:52 | history | edited | nilsun | CC BY-SA 3.0 | added 30 characters in body |
| Apr 10, 2016 at 9:41 | history | edited | nilsun | CC BY-SA 3.0 | added 495 characters in body |
| Apr 10, 2016 at 2:33 | history | edited | nilsun | CC BY-SA 3.0 | added 287 characters in body |
| Apr 10, 2016 at 2:22 | history | asked | nilsun | CC BY-SA 3.0 |