Hi,
attached is a patch that introduces a new permission 'access mail' (see http://drupal.org/node/315758 ).
| Comment | File | Size | Author |
|---|---|---|---|
| user.views_.inc_.patch | 1.05 KB | gurubert |
Hi,
attached is a patch that introduces a new permission 'access mail' (see http://drupal.org/node/315758 ).
| Comment | File | Size | Author |
|---|---|---|---|
| user.views_.inc_.patch | 1.05 KB | gurubert |
Comments
Comment #1
merlinofchaos commentedYou can't just use arbitrary strings that aren't in some hook_perm somewhere, and it's not Views responsibility to add permissions. Actually, I had thought I had taken this permission checking out, as it seems like a bad idea to me.
Comment #2
gurubert commentedHi merlinofchaos,
I know that, that's why I reference issue #315758: Add extra field for user email address where I attached a patch that creates this permission.
Comment #3
gurubert commentedComment #4
merlinofchaos commentedUnfortunately, I can't really look at features that require Drupal features that are only patched in. I really can't bother with features that are in -dev only and not yet released, either; especially when it would break things for everyone who doesn't have it.
In any case, I think having the permission there was the wrong idea. I'll remove it and add a warning to the description for the field. (If you want to file a patch to do that, I'd be happy, but it's not necessary as it's only 5 or so minutes of work when I get around to it).
Comment #5
dawehnerThis is not in drupal6 or drupal7. So make it postponed
Comment #6
voxpelli commentedAs has been stated previously by merlin this is not part of drupal core and therefor shouldn't be part of Views. As mentioned by dereine this is not part of either drupal 6 or 7 and there is no sign that this will be part of Drupal core.
If Views would have issues trailing every single core issue then Views issue queue would be huge. Since there has been no activity here for almost a year I'm closing this as a won't fix. If the referenced issue gets into drupal core then please open a new issue.