Missing sections/paragraphs

Created on 31 August 2025, about 1 month ago

Problem/Motivation

After installation, I can't find any element to be placed.

Steps to reproduce

On a fresh Drupal 11 site, add and enable content_templates along with quick_node_clone.
Add article. On the edit form, only the standard items appear, but neither can they be rearranged, e.g. in two columns, nor anything added.

Proposed resolution

There may be more dependencies like layout_discovery, layout_builder, paragraphs. Please add to the documentation how to setup on a "blank" site.

💬 Support request
Status

Active

Version

1.2

Component

Documentation

Created by

🇩🇪Germany thomas.wardin

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @thomas.wardin
  • 🇩🇪Germany a.dmitriiev

    Hi @thomas.wardin,

    The module itself doesn't provide any content templates, but gives you tools that you can create your own templates from the existing content items. So if you create a page with the structure you like and then you want to create more pages like this in the future, you can create a template from it and it will contain the items you need: paragraphs, media references, content references, etc.

    On content edit page, you should see the "Template" tab, when you click it you will see a form like this:

    If you provide the name and submit this form, the template with the structure of this node will appear in the list and you will be able to create new content items from this template.

    Please let me know if you need more information on this.

  • 🇩🇪Germany thomas.wardin

    So you want to correct the - IMHO - misleading description

    solution for creating and managing custom templates ... Templates can be easily created from existing nodes and can be customised later on.

    What's not defined in the existing nodes, cannot be added or changed by customization.

    Maybe, replacing the term "template" by "prototype" or "flavor" would be best, i.e. not using the term used for node templates.

  • 🇩🇪Germany breidert

    The text was changed from

    Content templates module provides a user-friendly and flexible solution for creating and managing custom templates to control the layouts of content (nodes) and streamline editorial workflow. It allows site administrators and content editors to create visually appealing templates for different types of content tailored to specific target audiences. Templates can be easily created from existing nodes and can be customised later on. With a single click, new content is created from a template, and a reference to the template is retained for easy retrieval of all nodes created from specific templates.

    to

    Content templates module provides an intuitive and flexible way to create and manage custom templates based on existing content (nodes). Existing pages can be reused as templates, or dedicated templates can be created from the ground up. This enables site administrators and content editors to design templates for different use cases. Templates can be organized by topic, and new content can be generated from a template with a single click. Each new page keeps a reference to the template it was created from, making it easy to retrieve and manage all content associated with a specific template.

    The relevant sentence that was confusing was changed to ... to create and manage custom templates based on existing content (nodes). Existing pages can be reused as templates, or dedicated templates can be created ...

  • 🇩🇪Germany thomas.wardin

    Wouldn't you think that

    ...can be created from ground up

    is equalky misleading given that "template" is a term used in theming,

  • 🇩🇪Germany breidert

    I was also thinking about the last part of the sentence ...can be created from ground up.

    @thomas.Wardin - Do you have a better suggestion for the whole sentence?

    Existing pages can be reused as templates, or dedicated templates can be created from the ground up.

  • 🇩🇪Germany thomas.wardin

    I'd suggest to use prototype or model or the like in lieu of template. This would most likely avoid any confusion.

Production build 0.71.5 2024