[TYPO3-english] backend layout

[Katja Lampela]

Hi,

8.11.2014 15.36, Jigal van Hemert kirjoitti:
> On 07/11/2014 15:00, Philipp Gampe wrote:
>> Actually you can do this, be using global conditions inside the backend
>> layout definition. e.g.
>
> That would actually change the structure of the BE layout in a way that
> it doesn't look like the frontend anymore.
> Using mod.SHARED.colPos_list the blocks that aren't accessible are still
> shown as areas in the layout, but with a different styling which makes
> it clear that you can't put content in them.
>

In my case just simplifying the backend view works best, because I want 
to keep the layout as simple as possible for the regular content editor.

I use sliding columns. In root page I have the easily editable header 
and footer columns that I don't want content editors to be able to edit. 
So I want to offer them different and simple edit view on that page.

This is how I did it:

backend_layout {
	colCount = 2
	rowCount = 4
	rows {
		1 {
			columns {
				1 {
					name = HEADER (only for admins)
					colspan = 2
					colPos = 3
				}
			}
		}
		2 {
			columns {
				1 {
					name = WIDE (only for admins)
					colspan = 2
					colPos = 5
				}
			}
		}
		3 {
			columns {
				1 {
					name = LEFT CONTENT
					colPos = 0
				}
				2 {
					name = RIGHT CONTENT
					colPos = 7
				}
			}
		}
		4 {
			columns {
				1 {
					name = FOOTER (only for admins)
					colspan = 2
					colPos = 4
				}
			}
		}
	}
}
[globalVar = BE_USER|user|uid = 5]
backend_layout.rows.1.columns.1 >
backend_layout.rows.2.columns.1 >
backend_layout.rows.4.columns.1 >
[GLOBAL]

So the backend editor uid5 can see only the columns CONTENT LEFT and 
CONTENT RIGHT.

I do wonder though why there is no backend usergroup condition.

Anyway, this works perfectly, thanks Philipp again!

-- 
Kind regards,
Katja Lampela
www.lieska.net