Project

General

Profile

Actions

Feature #67884

closed

display 'lost' CEs

Added by Bernd Wilke almost 9 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Backend User Interface
Target version:
Start date:
2015-07-02
Due date:
% Done:

100%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:
On Location Sprint

Description

gather all CEs which are not assigned to a valid column of the current BE-layout (or one of those metacolumns like 18181(fluid_content) or -2(gridelements)) and show them at the end of the page IF the user has checked to display 'lost' CEs, which could be an additional option to the page view.

the list of special columns (metacolumns) should be changeable, so that extensions like fluid_content or gridelements add their special column to the exception list.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Feature #76564: add a system to retrieve "lost" content elements if list view is not availableClosed2016-06-09

Actions
Actions #1

Updated by Jo Hasenau almost 9 years ago

  • Status changed from New to Accepted
  • Assignee set to Jo Hasenau
Actions #2

Updated by Susanne Moog almost 9 years ago

  • Target version changed from 7.4 (Backend) to 7.5
Actions #3

Updated by Benni Mack over 8 years ago

  • Target version changed from 7.5 to 7 LTS
Actions #4

Updated by Benni Mack over 8 years ago

  • Target version changed from 7 LTS to 8 LTS
Actions #5

Updated by Riccardo De Contardi almost 8 years ago

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

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!]
Actions #6

Updated by Riccardo De Contardi over 7 years ago

  • Target version changed from 8 LTS to 9.0
Actions #7

Updated by Benjamin Kott about 7 years ago

  • Sprint Focus set to On Location Sprint
Actions #8

Updated by Gerrit Code Review about 7 years ago

  • Status changed from Accepted to Under Review

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

Actions #9

Updated by Gerrit Code Review about 7 years ago

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

Actions #10

Updated by Gerrit Code Review about 7 years ago

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

Actions #11

Updated by Gerrit Code Review about 7 years ago

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

Actions #12

Updated by Gerrit Code Review about 7 years ago

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

Actions #13

Updated by Gerrit Code Review about 7 years ago

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

Actions #14

Updated by Gerrit Code Review about 7 years ago

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

Actions #15

Updated by Gerrit Code Review about 7 years ago

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

Actions #16

Updated by Gerrit Code Review about 7 years ago

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

Actions #17

Updated by Gerrit Code Review about 7 years ago

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

Actions #18

Updated by Gerrit Code Review about 7 years ago

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

Actions #19

Updated by Gerrit Code Review about 7 years ago

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

Actions #20

Updated by Gerrit Code Review about 7 years ago

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

Actions #21

Updated by Jo Hasenau about 7 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #22

Updated by Gerrit Code Review about 7 years ago

  • Status changed from Resolved to Under Review

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

Actions #23

Updated by Gerrit Code Review about 7 years ago

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

Actions #24

Updated by Gerrit Code Review about 7 years ago

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

Actions #25

Updated by Jo Hasenau about 7 years ago

  • Status changed from Under Review to Resolved
Actions #26

Updated by Claus Due almost 7 years ago

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.

Actions #27

Updated by Nicole Cordes over 6 years ago

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

Actions #28

Updated by Coders.Care Extension Team over 6 years ago

  • Related to deleted (Task #67134: The core must provide structured content elements which are configurable similar to backend layouts out of the box)
Actions #29

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF