Timeline for How do you theme the book module?
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 7 at 10:46 | history | edited | avpaderno♦ |
edited tags
|
|
| Jun 5 at 20:11 | comment | added | Clive♦ | Yeah, after a re-read I can understand the confusion. Hopefully the module in the answer will solve the problem | |
| Jun 5 at 20:09 | answer | added | Clive♦ | timeline score: 0 | |
| Jun 5 at 16:48 | comment | added | J C | @Clive Thank you for that perspective. The reason I think of it the other way around is that they are showing up in the html view when viewing the page, if they were just meta data, I would not expect them to be displayed. | |
| Jun 5 at 15:57 | comment | added | Clive♦ | I need to understand why all the fields shown in the "form display" of the content type are not available in the other tabs I would put that the other way around to be honest - why would you expect "Publishing status', "URL alias", "URL redirects", "Moderation State", etc. to be available as HTML content to render on the front end? They're intended to be metadata. They're not listed under "Manage fields" because only fields created with the field UI are listed there (body field the only exception, for new content types, which is automatically added, but is still "owned" by field UI) | |
| Jun 5 at 15:41 | history | edited | J C | CC BY-SA 4.0 |
added 107 characters in body
|
| Jun 5 at 14:00 | history | edited | J C | CC BY-SA 4.0 |
Trying to clarify question
|
| Jun 5 at 8:50 | comment | added | leymannx | Yes, you need to enable Twig debugging and then inspect the markup to see which templates are used: drupal.stackexchange.com/a/316894/15055. Then you copy the templates from the original directory into your custom theme's templates directory and start theming. | |
| Jun 5 at 3:15 | comment | added | Patrick Kenny |
It's not clear what your question is. content is not a field; it is a placeholder that is replaced by another template that contains the body field (and other custom fields that you may add via the UI). Twig templates are stacked-- the html template contains the page template, which contains the entity/book template, which contains the book/body template, and so on. So you need to find the right template to customize whatever you want, which you can do with twig debugging: drush twig:debug on
|
|
| Jun 5 at 2:18 | review | Close votes | |||
| Jun 21 at 3:08 | |||||
| Jun 5 at 1:52 | history | edited | mona lisa |
The question doesn’t mention layout builder.
|
|
| S Jun 4 at 23:54 | review | First questions | |||
| Jun 5 at 14:50 | |||||
| S Jun 4 at 23:54 | history | asked | J C | CC BY-SA 4.0 |