2. Peter Kraume
Senior TYPO3 Developer / bgm websolutions
Member of the Board TYPO3 Association
Twitter: @cybersmog
Mail: peter.kraume@typo3.org
Slides: http://de.slideshare.net/pk77/
3. Why should I customize the Backend?
• Acceptance by the Editors increases a lot
• Much better productivity
• Less possibilities for Editors to make „Mistakes“
• Training of Editors is a lot easier
• Add an extra part to your quotes for Backend user rights and
Backend optimization!
• It pays off for sure!
4. What do we need to customize the Backend?
• Settings in Backend Extension
• News for Editors
• Notes in the Backend
• Users & User Groups
• Access Module
• Page & User TSConfig
• Guided Tours
16. Notes for Editors in the Page Module
• There are different note
categories
• Each category has it’s own color
in the Page Module
17. Notes for Editors in the Page Module
• Personal notes are only visible for yourself!
18. Users & User Groups
• User Group Naming Concept:
• Editors
• _Rights
• _DB Mount
• _File Access
• _Access
• Distribute rights in small pieces
19. Users & User Groups
• User Groups „_Rights: *“
• contains access to modules, tables, page types, allowed
excludefields, content elements and languages
• Examples:
• _Rights: All Backend Users
• _Rights: Content Elements / Plugins
• _Rights: News
• _Rights: Forms
• _Rights: Products
20. Users & User Groups
• User Groups „_DB Mount: *“
• contains only the DB Mounts, the editors should have in their page
tree
• Examples:
• _DB Mount: all
• _DB Mount: subtree A
• _DB Mount: subtree B
21. Users & User Groups
• User Groups „_File Access: *“
• contains all file related rights like the File Mounts, file operations
permissions and FAL records
• Examples:
• _File Access: All
• _File Access: News
22. Users & User Groups
• User Groups „_Access: *“
• these groups are used in the Access Module to grant read and
write access
• Examples:
• _Access: All
• _Access: subtree A
• _Access: subtree B
23. Users & User Groups
• User Groups „Editors: *“
• container groups which only inherit from other user groups
• these are the only user groups assigned to individual users
• Examples:
• Editors: All
• Editors: Events
• Editors: TYPO3 Association
• Editors: News
24. Users & User Groups
• User Records
• only contain personal data and „Editor: *“ user groups
• don’t override settings from user groups here
• create a user group instead
26. Page & User TSConfig
• Almost everything in the TYPO3 Backend can be modified via Page
and User TSConfig
• rename fields
• remove fields
• remove superfluous select field items
27. Page & User TSConfig
Page TSConfig:
• set proper user group
permissions for new pages
• The groupid must match the
uid of the _Access user
group
# _Access:All
TCEMAIN.permissions {
groupid = 1
user = show, editcontent, edit, new, delete
group = show, editcontent, edit, new, delete
everybody = show
}
# _Access: subtree A
[PIDinRootline = 100]
TCEMAIN.permissions {
groupid = 2
}
[global]
# _Access: subtree B
[PIDinRootline = 200]
TCEMAIN.permissions {
groupid = 3
}
[global]
28. Page & User TSConfig
Page TSConfig:
• set flag icon and name for
default language
• Default settings for
checkboxes in list module
• hide records of certain
database tables
mod {
SHARED{
defaultLanguageFlag = de
defaultLanguageLabel = Deutsch
}
web_list{
enableDisplayBigControlPanel = activated
enableClipBoard = activated
enableLocalizationView = activated
}
}
# hide records of certain database tables
[PIDinRootline = 1234]
mod {
web_list {
hideTables = tx_extkey_tablename
}
}
[global]
31. Page & User TSConfig
User TSConfig:
• set default values for new
users
• remove fields in user
settings
setup{
# set default values for new users
default {
emailMeAtLogin = 0
}
# remove fields
fields {
avatar.disabled = 1
}
}
# enforce above settings also for existing users
setup.override < setup.default
32. Guided Tour through the Backend
• EXT:guide
• provides a guided tour
through the TYPO3 Backend
• Extension authors can hook
into this toolset and create
interactive tours for their
own extensions
33. General Hints
• General Hints:
• there is no „one concept fits all“ approach!
• use the „description“ field in the user group records to document
the intention of the user group
• do extensive testing together with your customer
35. Thank you!
Twitter: @cybersmog
Mail: peter.kraume@typo3.org
Slides: http://de.slideshare.net/pk77/
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.