Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Get happy Editors with a suitable TYPO3 Backend Configuration

1,137 views

Published on

This talks explains how to set up a proper permission concept for editors and how to configure the TYPO3 backend to show only the fields the editor really needs. Additional topics are login news, notes for editors, settings in the backend extenion, the rich text editor, context sensitive help (CSH) and guided tours through the TYPO3 backend.

Published in: Internet
  • Be the first to comment

Get happy Editors with a suitable TYPO3 Backend Configuration

  1. 1. Get happy Editors with a suitable TYPO3 Backend Configuration TYPO3 Developer Days 2017 July 16th, 2017
  2. 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. 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. 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 • Rich Text Editor (CKEditor) • Guided Tours in the Backend
  5. 5. Settings in the Backend Extension
  6. 6. Settings in the Backend Extension
  7. 7. Settings in the Backend Extension
  8. 8. Settings in the Backend Extension
  9. 9. Settings in the Backend Extension
  10. 10. System News on Login Screen
  11. 11. System News on Login Screen
  12. 12. System News on Login Screen
  13. 13. System News on Login Screen
  14. 14. Notes for Editors in the Page Module
  15. 15. Notes for Editors in the Page Module
  16. 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. 17. Notes for Editors in the Page Module • Personal notes are only visible for yourself!
  18. 18. Users & User Groups • User Group Naming Concept: • Editors • _Rights • _DB Mount • _File Access • _Access • Distribute rights in small pieces
  19. 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. 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. 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. 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. 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. 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
  25. 25. Access Module
  26. 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. 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. 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]
  29. 29. Page & User TSConfig Page TSConfig: • disable fields • remove select box items • extend select boxes TCEFORM{ pages{ subtitle.disabled = 1 shortcut_mode { keepItems = 0,1 } } tt_content{ section_frame.label = new label text section_frame { removeItems = 1,5,6,10,11,12,20,21,66 addItems.98 = item98 addItems.99 = item99 } } }
  30. 30. Page & User TSConfig Page TSConfig: • set default values TCAdefaults{ pages{ shortcut_mode = 1 } tt_content{ imagecols = 1 filelink_size = 1 image_zoom = 0 } }
  31. 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. 32. Rich Text Editor (CKEditor) • CKEditor was introduced in TYPO3 8 • much easier integration • different configurations depending on intended use possible • See talk of Frans Saris for details: https:// www.slideshare.net/ FransSaris/htmlarea-to- ckeditor-creates-presets- and-your-own-plugin
  33. 33. Guided Tours through the Backend
  34. 34. Guided Tours through the Backend • EXT:guide • provides several guided tours through the TYPO3 Backend • Extension authors can hook into this toolset and create interactive tours for their own extensions • https://github.com/tdeuling/ typo3-guide/ • https://typo3.org/extensions/ repository/view/guide
  35. 35. 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
  36. 36. Questions?
  37. 37. 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.

×