Fix finding child content-type elements in stage-builder #869
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description (*)
Fixes a bug whereby child content-type elements will not be found, where other types of elements also exist at the same level.
Manual testing scenarios (*)
master.html:
preview.html:
It is possible to create this content type in Pagebuilder, and the correct result is rendered into the database and on the frontend. However, Pagebuilder cannot then load up the content back into the stage - the presence of the
<li>
element causes only the last item to be found, and<div class="swiper-scrollbar">
causes even that to be forgotten.This small fix corrects this, and all types of content can now be loaded into the stage correctly.
Checklist
Resolved issues: