TYPO3 Core

Steps to reproduce:

• Hide the field by TSConfig (TCEFORM.tt_content.colPos.disabled = 1) or for editors through access lists in a BE-group
• Go to the page module and create a content element in any available column, except the one with colPos=0

Result: the content element is always created with colPos=0, also when created in another column. That may be fine in the List-module, in the Page-module this is very much unexpected and undesired behaviour.

There is a difference in behaviour between hiding through TSConfig or Access Lists:

If 'colPos' is not enabled in the access list for editors, they are NOT AT ALL able to move content the desired columns: you can drag content to another column in the Page Module and the content appears to be moved correcty, but if you reload the page in the backend you'll find that nothing has changed.

• not enabling colPos in an access list breaks moving content to other columns completely for non-admins
• hiding colPos in TSConfig also results in new content always created with colPos=0, regardless in which column you create it. But in this case, you can drag it to the right column afterwards, but of course that's a drag :-)