TYPO3 Core

Imagine the following scenario:

1) create two backend layouts, named "test" and "test2"

this is "test":

backend_layout {
    colCount = 1
    rowCount = 2
    rows {
        1 {
            columns {
                1 {
                    name = Main
                    colPos = 0
                }
            }
        }
        2 {
            columns {
                1 {
                    name = Bottom
                    colPos = 1
                }
            }
        }
    }
}

and this is "test2":

backend_layout {
    colCount = 1
    rowCount = 2
    rows {
        1 {
            columns {
                1 {
                    name = Main
                    colPos = 0
                }
            }
        }
        2 {
            columns {
                1 {
                    name = Bottom
                    colPos = 2
                }
            }
        }
    }
}

2) create a page and assign "test"
3) create a content element inside the "Bottom" column and save.
4) edit the page and switch backend layout to "test2"

Result:¶

in page view the content element disappears (is "lost"), as it doesn't have a valid colPos anymore; the only easy method to have it back is using the list view (which is not meant to be used to manipulate tt_content records and in the future this practice could be disallowed).

possible solution:¶

(thanks to Mathias Schreiber for the suggestion) Add a flash message in page view with a message like:

"There are CEs that cannot be displayed for Reason X, click here to migrate them to an available column" 

or add two buttons:

"There are CEs that cannot be displayed for Reason X

     [Migrate to an available column] [delete them!]