Needs work
Project:
XML sitemap
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
14 Feb 2012 at 19:39 UTC
Updated:
6 Sep 2018 at 10:22 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Anonymous (not verified) commentedCan't this be accomplished with a custom module using hooks?
Comment #2
traviscarden commentedDoubtless it can—as can most anything—but is that the important question? It seems to me the separation of administrative from editorial permissions is essential for any module designed for general application and that only uncommon functionality should require custom development. (After all, not all Drupal users are developers.) I propose that the cost of adding a second permission is not comparable to the benefit of having it. A quick perusal of the issue queue suggests that other users are looking for more granular permissions, too. Do you have a specific objection to obliging them?
Comment #3
Anonymous (not verified) commentedOk, but postponed until a first release.
Comment #4
ruudvanoijen commentedI've created a patch for this. To have 3 permissions. One for advanced settings, one for managing xml sitemap. One for adding content to the xml sitemap.
Comment #6
ralphvdhoudt commentedBetter patch
Comment #7
brockfanning commentedTrying a re-roll to work with the latest dev.
Comment #9
paulvandenburg commentedConfirmed working reroll of the patch. Sadly interdiff is having difficulty computing a proper interdiff between 5 (#6) and #7.
But perhaps we should fix the failing tests before marking this RTBC.