drupal backend and admin
DESCRIPTION
How to properly setup Drupal administration backend administration area, permissions, roles. Modules that might be useful for admins and content managers.TRANSCRIPT
![Page 1: Drupal backend and admin](https://reader030.vdocuments.site/reader030/viewer/2022012316/53fd9afc8d7f72a81c8b49ca/html5/thumbnails/1.jpg)
Drupal Backendand Admin
Alex Milkovskyi
![Page 2: Drupal backend and admin](https://reader030.vdocuments.site/reader030/viewer/2022012316/53fd9afc8d7f72a81c8b49ca/html5/thumbnails/2.jpg)
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
![Page 3: Drupal backend and admin](https://reader030.vdocuments.site/reader030/viewer/2022012316/53fd9afc8d7f72a81c8b49ca/html5/thumbnails/3.jpg)
Topic
How to properly setup ● Drupal administration backend ● administration area, ● permissions, ● roles. Useful modules for admins and content managers.
![Page 4: Drupal backend and admin](https://reader030.vdocuments.site/reader030/viewer/2022012316/53fd9afc8d7f72a81c8b49ca/html5/thumbnails/4.jpg)
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?
![Page 5: Drupal backend and admin](https://reader030.vdocuments.site/reader030/viewer/2022012316/53fd9afc8d7f72a81c8b49ca/html5/thumbnails/5.jpg)
The Problem
![Page 6: Drupal backend and admin](https://reader030.vdocuments.site/reader030/viewer/2022012316/53fd9afc8d7f72a81c8b49ca/html5/thumbnails/6.jpg)
Problem
● Drupal is powerful framework, provides a plenty of ways for customization
● But does the customer need access to all this settings?
![Page 7: Drupal backend and admin](https://reader030.vdocuments.site/reader030/viewer/2022012316/53fd9afc8d7f72a81c8b49ca/html5/thumbnails/7.jpg)
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
![Page 8: Drupal backend and admin](https://reader030.vdocuments.site/reader030/viewer/2022012316/53fd9afc8d7f72a81c8b49ca/html5/thumbnails/8.jpg)
Suggestion
For example: ● not “taxonomy terms” but “Catalog
categories”, “Brands”● not “content types” but “News”, “Products”,
“Articles”
![Page 9: Drupal backend and admin](https://reader030.vdocuments.site/reader030/viewer/2022012316/53fd9afc8d7f72a81c8b49ca/html5/thumbnails/9.jpg)
Solution
![Page 10: Drupal backend and admin](https://reader030.vdocuments.site/reader030/viewer/2022012316/53fd9afc8d7f72a81c8b49ca/html5/thumbnails/10.jpg)
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
![Page 11: Drupal backend and admin](https://reader030.vdocuments.site/reader030/viewer/2022012316/53fd9afc8d7f72a81c8b49ca/html5/thumbnails/11.jpg)
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
![Page 12: Drupal backend and admin](https://reader030.vdocuments.site/reader030/viewer/2022012316/53fd9afc8d7f72a81c8b49ca/html5/thumbnails/12.jpg)
Administration Menu Source
![Page 13: Drupal backend and admin](https://reader030.vdocuments.site/reader030/viewer/2022012316/53fd9afc8d7f72a81c8b49ca/html5/thumbnails/13.jpg)
SimplifySimplify allows particular fields to be hidden from the user interface.
![Page 14: Drupal backend and admin](https://reader030.vdocuments.site/reader030/viewer/2022012316/53fd9afc8d7f72a81c8b49ca/html5/thumbnails/14.jpg)
Better Formats
![Page 15: Drupal backend and admin](https://reader030.vdocuments.site/reader030/viewer/2022012316/53fd9afc8d7f72a81c8b49ca/html5/thumbnails/15.jpg)
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
![Page 16: Drupal backend and admin](https://reader030.vdocuments.site/reader030/viewer/2022012316/53fd9afc8d7f72a81c8b49ca/html5/thumbnails/16.jpg)
![Page 17: Drupal backend and admin](https://reader030.vdocuments.site/reader030/viewer/2022012316/53fd9afc8d7f72a81c8b49ca/html5/thumbnails/17.jpg)
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.
![Page 18: Drupal backend and admin](https://reader030.vdocuments.site/reader030/viewer/2022012316/53fd9afc8d7f72a81c8b49ca/html5/thumbnails/18.jpg)
DraggableViews
![Page 19: Drupal backend and admin](https://reader030.vdocuments.site/reader030/viewer/2022012316/53fd9afc8d7f72a81c8b49ca/html5/thumbnails/19.jpg)
Other hints
● NO enabled dev modules on production● Environment Indicator● VBO● Field Permissions● CKEditor● IMCE● Form Cancel Button
![Page 20: Drupal backend and admin](https://reader030.vdocuments.site/reader030/viewer/2022012316/53fd9afc8d7f72a81c8b49ca/html5/thumbnails/20.jpg)
Thank you!