Timeline for Views not picking up custom field plugin in views UI
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 28 at 14:24 | comment | added | Hodgekins | Thanks for your comment. It cleared a lot of things up. It seems there was something fundamental I was missing (what you said). | |
| May 28 at 14:23 | vote | accept | Hodgekins | ||
| May 28 at 12:40 | answer | added | 4uk4 | timeline score: 1 | |
| May 28 at 12:40 | comment | added | Clive♦ | It's a bit more complicated than that - so far you've created a field handler, not a field. Next step is to assign that handler to one or more fields; exactly how you do that depends on the desired outcome and what the data relates to. What is "open tickets" at its core? Does it represent a field on a content type? Or is it "virtual", e.g. a bundling of data from a few different fields? Or is to more higher-level than that; generic to any entity type, or maybe just a single global value without context? | |
| May 28 at 12:13 | history | asked | Hodgekins | CC BY-SA 4.0 |