Drupal backend and admin
Download as PDF, PPTX4 likes1,258 views
The document details Oleksandr (Alex) Milkivskyi's background as a Drupal developer and outlines recommendations for setting up the Drupal administration backend. It emphasizes the importance of customizing user roles and permissions to ensure that end-users see only relevant, understandable content in the backend. The document also discusses various useful modules for enhancing administrative efficiency and user experience.
Drupal backend and admin
- 1. Drupal Backend and Admin Alex Milkovskyi
- 2. About me: Oleksandr(Alex) Milkovskyi ● Drupal Developer at Bright Solutions GmbH ● Student at FH Technikum Wien ● Met Drupal in January 2010 ● 2010-2012: Drupal Frontend Developer, Themer, Sitebuilder ● 2012-2014: Drupal Backend Developer ● https://drupal.org/user/1761220 a.milkovsky
- 3. Topic How to properly setup ● Drupal administration backend ● administration area, ● permissions, ● roles. Useful modules for admins and content managers.
- 4. Problem ● How do you usually setup Drupal backend for the end user? ● Developers that deliver projects to the end customer just with the superuser($uid=1). ● Is it good or bad?
- 5. The Problem
- 6. Problem ● Drupal is powerful framework, provides a plenty of ways for customization ● But does the customer need access to all this settings?
- 7. Suggestion The customer wants to see in the website backend: ● only things that he already can understand ● the words that he uses in his business
- 8. Suggestion For example: ● not “taxonomy terms” but “Catalog categories”, “Brands” ● not “content types” but “News”, “Products”, “Articles”
- 9. Solution
- 10. Roles ● Superuser($uid=1) - user only for development(not a role) ● Developer - administration role ● Administrator - content manager role. Has only permissions to manage general site settings, some nodes and taxonomy vocabularies. ● SEO - sometimes necessary. ● Authenticated user ● Other
- 11. Admin role This module is a little helper to maintain an administrator role which has all available permissions. as the core function that was added in D7 seems to fall short of expectations; this module has been ported to D7
- 13. Simplify Simplify allows particular fields to be hidden from the user interface.
- 14. Better Formats
- 15. Taxonomy access fix ● adds permission per vocabulary: "add terms in X" ● changes the way vocabulary specific permissions are handled ● changes the Taxonomy admin pages' access checks ● alters the vocabularies overview table to show only what you have access to edit or delete
- 17. Taxonomy Term Status This module adds a status-flag to taxonomy terms. Using this flag it is possible to specify whether terms should be published or not. Users with the appropriate permission may access unpublished terms.
- 18. DraggableViews
- 19. Other hints ● NO enabled dev modules on production ● Environment Indicator ● VBO ● Field Permissions ● CKEditor ● IMCE ● Form Cancel Button
- 20. Thank you!