TYPO3 Core

you don't even have to use gridelements of flux to stumble upon this kind of issue... Imagine the following scenario (I report here the text of #76564):

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
                }
            }
        }
    }
}

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

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" 

"There are CEs that cannot be displayed for Reason X

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

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53040

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53040

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53040

Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53040

Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53040

Patch set 7 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53040

Patch set 8 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53040

Patch set 9 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53040

Patch set 10 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53040

Patch set 11 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53040

Patch set 12 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53040

Patch set 13 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53040

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53082

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53082

you don't even have to use gridelements of flux to stumble upon this kind of issue.

True, but after applying this patch, now if you use those extensions all child content gets reported as lost even though it was rendered and there's no way to avoid that without adding the column to the page layout and thereby render duplicated content elements.

I don't mean to sound harsh here but I find it quite odd that you would mention these extensions as a way to experience the symptom - and then go on to create a solution that completely breaks one of those solutions... unfortunately, this has caused quite a negative effect at least for Flux, to a degree where Flux will be broken unless I manage to sneak a new signal dispatching in before the release of v9.

I'm not too happy about this, to tell you the truth.

Is there any follow up available already? What is the plan for the extensions (content elements) using IRRE with tt_content elements? Would be cool if you would add me as reviewer to any additional patch.

Thanks