Closed (fixed)
Project:
Conference Organizing Distribution Support Modules
Version:
7.x-1.x-dev
Component:
cod_base
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
5 Jul 2012 at 21:01 UTC
Updated:
4 Jan 2014 at 02:05 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
saltednutAgreed, this would be useful - is this role a part of cod_base?
Comment #2
twardnw commentedcod_base feels to me like the appropriate place to include this role
Comment #3
dsdeiz commentedPatch attached. Adds "Content editor" role which has similar permissions as the "Site administrator". I'm guessing I can't add content type related permissions on the role until the other submodules that create new content types are ported.
Comment #4
mjonesdinero commentedHi i apply the patch on comment #3 and the patch was apply clean.. and from what on the comment said// it adds "Content Editor" role with same permission from the site administrator..
But permissions on content type is still not their as what stated on the comment.
Comment #5
ezra-g commented+1 for this type of role.
Do you see this role as having the "administer content types" or the ability to edit any node on the site, or just a restricted set of content types?
If the ability to edit nodes or content types is site-wide, we should call this role "content administrator" to signal that this is a role that should only be given to trusted users.
Comment #6
juampynr commentedAgree, content administrator makes more sense.
Here is the patch updated with that role name.
Comment #7
twardnw commentedpatch applies clean, creates role, has no permissions at this point.
Comment #8
twardnw commentedI went ahead and added the 'administer content' permission to the feature.
Comment #9
mjonesdinero commentedhi patch applies cleanly, though have a question on #8 "administer content" is not checked when i applied the patch.
Comment #10
juampynr commented@mjonesdinero, did you revert cod_base feature after applying the patch?
Comment #11
sheldonkreger commentedI had the same problem as mjonesdinero. New patch solves, should be good to go!
Comment #12
mjonesdinero commentedapply the patch on #11 and "administer content" is checked when i applied the patch.
@juampy.. thanks for the info need to revert the features after applying the patch
Comment #13
primerg commentedtested with new install of cod and dev version of cod_support.
- role is there with the administer problem
- experienced that it wasn't working. can be fixed if you check the "View published content". this one is being added in http://drupal.org/node/1661620 . i think apply that first?
Comment #14
twardnw commentedSo, maybe I don't understand what the 'administer content' permission gains a user? Assigned a user to the role, but they can't edit anything or access anything under /admin and pieces of content have no edit links...
Comment #15
jackbravo commentedRe roll of the patch, adding the "access content overview" permission" so that the user can go to "/admin/content". But right now the user has no way to go there (no menu-item) except writing the URL on his browser.
Comment #16
dsdeiz commentedPatch applies cleanly on my end.
Comment #17
jackbravo commentedAnd does it work? So we can mark as reviewed. You should be able to edit any node and go to /admin/content once applied if you have a user with role content editor.
Comment #18
japerryRe-rolled this patch to give a few more permissions and make it compatible with the newly committed administrator patch for D7.
Requires Features 7.x-1.0
Comment #19
ezra-g commentedDiscussed with japerry: We should grant permissions from the other roles to the 'administrator' role.
Comment #20
japerryAdded roles and fixed problem with only anon users getting access to content. ;-)
Comment #21
ezra-g commented#20 doesn't apply.
Comment #22
sheldonkreger commentedYes, 20 failed to apply for me as well. See attached image.
Comment #23
japerryLets try this one instead
Comment #24
ezra-g commentedThis export includes orphaned permissions for Webform, which is not a dependency of COD_Base. #1673028: new role: content editor.
Comment #25
twardnw commentedthe latest cod_support is showing it as a dependency
Comment #26
ezra-g commentedWebform is not a dependency of COD Base: http://drupalcode.org/project/cod_support.git/blob/refs/heads/6.x-1.x:/c....
Per #24, this needs to be re-rolled to remove the Webform permissions.
Comment #27
japerryWebform removed, and content editor role added
Per this: 4a1e817715d44a917520e5dfe1b9f46dbd78f086