Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.COD Base is showing an overridden state as soon as it is enabled, specifically in the Field Permissions section, but it is not identifying which permission is overridden.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | cod_support-cod_base_feature-1670284-1.patch | 8.77 KB | twardnw |
| Screen Shot 2012-07-03 at 2.39.21 PM.png | 21.72 KB | twardnw |
Comments
Comment #1
twardnw commentedSo I recreated the feature with no changes made. Looking at the patch file, it looks like the fields now have a 'locked' setting, which is '0' in every case. Features also changed the way it comments, comments now end with a period:
Comment #2
gregglesThis looks good on a visual review and applies cleanly to 7.x-1.x-dev. I didn't actually test it.
Comment #3
sheldonkreger commentedPatch in 1 also applied cleanly for me, and resolved the "override" issue in COD Base.
Comment #4
saltednutPatch applies cleanly. Enabling cod_base shows its no longer overridden. Looks RTBC!
Comment #5
sheldonkreger commentedPlease note that patch #3 in http://drupal.org/node/1672922 relies on #1 in this thread.
Comment #6
cafuego commentedYup, +1 for RTBC here as well.
Comment #7
ezra-g commentedLooks like this would be resolved as part of the re-exporting that would happen to fix #1477754: Rename "site administrator" role to "administrator", which means it's either a duplicate or postponed.
Comment #8
japerryLooking at this issue brings some complicated issues -- I think most sites are going to have varying user permissions.
I think an alternative is having a set of sane permissions set by the cod distribution installer, and not by features. Permissions start to get into the content realm since conferences will almost always vary how they want to do this.
Also, cod_events and other features implementing permissions will show as overridden. Because of this, and the idea to keep features default as much as possible, we shouldn't put permissions in the features.
Comment #9
japerryFixed in alpha2 by putting the administrator permissions in the install by default
Comment #10
gregglesThanks for the work, Jakob.
It would be nice if you could link from the comment closing an issue to the commit message where the change was made (and ideally post a patch prior to committing it). I understand when sprinting things happen quickly so even just committing and linking (instead of posting the patch) seems reasonable.