Problem/Motivation
Generally, description pages can be reached by anonymous or low-permissioned users, but the page often links to admin pages. The user will then not be able to reach those pages, due to wholly appropriate restrictive permissions.
Proposed resolution
Figure out a consistent way to display a need for admin permissions to users. Apply this to all the description pages.
Maximize all the links, so that there aren't any paths shown in description pages that are not also links. Doing this in follow-up: #2976202: Ensure that all description page paths are clickable
Remaining tasks
User interface changes
API changes
Data model changes
Original issue summary:
People can get to the examples/node-type-example
path as long as they have access content
permission, which doesn't guarantee that they also have permission to administer content types. If they DO have permission to administer content types, then showing the link to the admin/structure/types
path is fine. If they do NOT have permission to administer content types, then we should just show the path name as literal text as we have done with the admin/structure/types/add
information on the list item.
Comments
Comment #2
vegantriathleteComment #3
Mile23I think we should present links where possible, and the routing system will figure out whether the user has access.
Otherwise we end up making a complex description page with not a lot of gain.
We should have some way of showing that you might need to be logged in and have permissions in order to do this, but it's also somewhat assumed throughout examples that you're an admin user.
Comment #4
Mile23Splitting off link-ifying everything here: #2976202: Ensure that all description page paths are clickable
Rescoping here so we can figure out how to effectively remind users to log in as an admin, without too much maintenance hassle.