on 2024 Mar 15 3:55 AM
A component is linked to a slot, which has a list of nested components (1:N), each of the nested components has one attached (1:1).
For example, in the FAQ section, there is a component responsible for a group of questions and answers, but each of the question-answer pairs is not a terminal component, but a wrapper over CMSParagraph which is in turn the terminal one. As a result, there are three levels of nesting: Group->Wrapper->CMSParagraph. The wrapper has some extra info and supports not only CMSParagraph, but basically any time of components. Not I designed this, but I am seeking how to tame such existing structure.
DIVs are configured properly — in the resulting HTML of the frontend there all levels have their markups, like class="smartEditComponent" data-smartedit-component-id="FiltersContent-faq" data-smartedit-component-uuid="...." data-smartedit-component-type="ContentSlot" data-smartedit-catalog-version-uuid="..../Online" - this is the example for a contentslot, but similar is for the components. In the simpler cases, our markup works fine. The problem is with nested components, 3 levels.
Now, if you open Smartedit with such a setup, the following oddities are observed:
Request clarification before answering.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.