I have a section in which only content from the templates pages and home are displayed:
templates: [pages, home]
I also have manual sorting active. However, manual sorting also takes into account content that appears in other sections, i.e. that uses other templates.
If I now start sorting, the element is not sorted at the drop point, but skips four elements, for example, because content from other templates would appear in between. This is of course confusing for the user.
How can I proceed so that this does not happen and only the filtered templates are taken into account for sorting?
What’s the expectation that should happen with those other listed/number/sorted pages? How should the pages in your section relate to those? And how would one avoid duplicate sorting numbers if the pages in the section should not take the other pages into account, but the other pages still have sorting numbers?
I think the more common setup would probably be that you have all pages that should be sorted in your section where you can sort them manually, but keep all other pages as unlisted (without sorting number).
The other pages that are based on different templates appear in other sections and actually have no connection to the main pages. However, I would like to be able to sort them in their section as well. Is that not possible in this case? Would the other content have to be based on a custom type instead of pages?
How would this work? You have two sets of pages, you want both of them to be numbered/sorted but independent of each other. That would inevitably lead to multiple sibling pages with the same sorting number.
Personally, I would still stick with pages, but my guess is that there are things to tie one set of pages together and others that tie the other set together - so maybe one set should rather go as subpages to a main page, bundling them together.
That makes sense to combine it into different subcontents. But how is the content bound together if there is no parent page? Do I need to create a hidden page for it?
Yes. Maybe if you give more concrete example what types of pages we’re talking about, we can make suggestions.
Here are two of the types:
Fragments are pages that can be inserted as block elements on normal pages. In other words, similar to widgets. I manage the contents of the Fragments page in a structure field.
Events are pages that consist of countless events. Each subpage is a data record for an event.
I would probably create for both types a top-level parent page:
fragments
1_one-fragment
2_another-fragment
events
1_an-events-page
an-event
another-event
2_another-events-page
If you have other top-level pages, I would probably keep those as listed pages and those container pages (fragments, events) unlisted.