#22903Page module - content assigned to a non-existent column
Description
When using the new backend layouts (aka “Grid View”), then any content element having “colPos” set to a number which doesn’t exist in the current layout is not visible in the Page module.
Having such a content element may now easily happen with the newly introduced backend layouts when switching the layout of the page (e.g. from one having 5 columns to one having only 2 columns).
The Page module should list content elements not assigned to any column of the currently set backend layout.
(issue imported from #M17525)
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.