Timeline for Add fields to a coded block and use them in a templated block
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 13, 2021 at 16:58 | vote | accept | Leo Woods | ||
| Jan 30, 2018 at 16:53 | comment | added | Leo Woods | Hi @4k4 Sorry I have tried to create an entity and bundles but I never am able to create something complete? What commands do I use to create an entity and bundle so that I can add fields to it? | |
| Jan 25, 2018 at 11:56 | comment | added | Leo Woods | Nice one thank you, that indeed makes a lot of sense, I shall give that a go | |
| Jan 25, 2018 at 7:27 | comment | added | 4uk4 | Yes, there are pro and cons, but the biggest pro is IMHO the image handling of the field ui, which is hard to implement in own code. If you don't want to clutter the block system with a lot of custom block types it could make sense to create a custom entity type (Console generates a twig template for it automatically) and then use a simple block plugin to place the entity including the template in a custom block.. | |
| Jan 25, 2018 at 0:18 | comment | added | Leo Woods | I suppose I just want a one off custom block and don't necessarily want it to be a replicable thing. I have quite a few use cases where this would make more sense. Also it is better for pushing up the code using versioning | |
| Jan 24, 2018 at 17:46 | comment | added | 4uk4 | Why not use the field ui and the preinstalled image field type? And what do you mean by programmatically, you can do all things from the field ui in code as well. | |
| Jan 24, 2018 at 14:53 | answer | added | CG Monroe | timeline score: 0 | |
| Jan 24, 2018 at 14:24 | history | asked | Leo Woods | CC BY-SA 3.0 |