1. make an upgrade wizard which tries to find these settings and creates backend layouts; this is rather complicated as the setting might apply to a subtree of the site
2. make an upgrade wizard which tries to detect the setting and explains how to solve it manually
3. only document it

Modified for Introduction Package with a new backend layout, see https://review.typo3.org/#/c/16793/

With #47071 we have updated the documentation of mod.SHARED.colPos_list so that the documentation says mod.SHARED.colPos_list has been removed.

The only thing that still needs to be done here is:

Remove mod.SHARED.colPos_list from the code completely.

Well - as usual - it is not that easy, since colPos_list and backend layouts are completely different things, with completely different tasks.

While backend layouts provide the structure as such, that will be available for a certain site, colPos_list is meant to restrict the access to these columns i.e. based on certain conditions.

AFAIK this has been working even together with backend layouts in TYPO3 4.x so removing it silently with 6.0 instead of fixing the bug will now result in additional problems for people who are upgrading from 4.5 LTS to 6.2 LTS.

IMHO we must revert the removal at least for 6.2, but actually this should be fixed in earlier versions as well.

There is no need for a compatibility layer, since this has been a working feature, that was broken with the patch you mentioned in the description.
Removing it without deprecation is against our CGL, so it currently could not be removed before TYPO3 6.4 or 7.0

Actually it should not be removed, since it is used for another purpose than just a "poor man's backend layout".

Agree with Joey,

The mentioned patch should be reverted and the issue should be fixed for all versions.

When having a backend layout, you sometimes want to prevent access to a certain column for some users/user groups. At one of my clients (a university) we are using the setting mod.SHARED.colPos_list together with backend layouts, and it works.

As mentioned by Jo colPos_list and backend layouts are completely different things. The first is for access, the second for structure.

+1 for reverting, backend layouts does in no way replace the functionality of mod.SHARED.colPos_list

Patrick Broens wrote:

As mentioned by Jo colPos_list and backend layouts are completely different things. The first is for access, the second for structure.

Not really true. The order of colPos_list also mattered and was used to identify the order of columns.

Peter Niederlag wrote:

+1 for reverting

reverting what? the layout change?

The question is: How to we deal with the situation. I see following possibilities:

1. Restore mod.SHARED.colPos_list only when no backend layouts are present
2. Restore mod.SHARED.colPos_list, but only ignore the order when backend layouts are present (using the info to hide containers with not matching ids)
3. Add a new option that adds the possibility to remove containers by colpos from backend layouts
4. Provide an Upgradewizard (or separate script) adding backend layouts if colPos_list is present (traversing the tree)

Prio I¶

1. (Re-)Introduce mod.SHARED.colPos_list or introduce a new setting (I don't care to much on the name)
2. Only purpose of the setting is to influence wether certain columns in dropdown-selections and the page-module are to be shown
3. The order of the columns should not be within the scope of this setting (I am fine if it is for core)

Nice to have¶

1. It might be nice to have both whitelisting as well as blacklisting options (something like colPos_showOnly and colPos_hide)
2. It might be nice to have influence on the way columns are hidden (something like colPos_hiddenLayout = hidden|readonly)

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

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

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

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

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

Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/32615

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

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

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

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

Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/32742

Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/32743