Hi,
I noticed anonymous people have the option to enter meta tags into a CCK content type I created. I would like to take that away. For some reason, when I am logged in as ADMIN, I only see one option for configuring access (administer meta tags - which of course should only be for admins).
In some video tutorials, I saw the ability to configure more. Am I missing something? I have attached a picture of what I see as ADMIN under permissions.
Thanks very much!
Steve
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | nodewords_perm.patch | 451 bytes | gleich |
| Screen shot 2010-07-11 at 7.27.50 PM.png | 15.44 KB | recoil |
Comments
Comment #1
Anonymous (not verified) commentedThat is not something handled by Nodewords.
The old permissions have been removed with the purpose to use a different module of the family to handle the permissions to edit meta tags. The idea was to have the following permissions:
Comment #2
that0n3guy commentedAny ETA on this "other module"? Is it already out their someplace?
Comment #3
that0n3guy commentedI'm going to mark this as a bug (rather than feature request) as it is something that was removed (we had permissions before) and is vital for th 1.12 release.
Comment #4
gleich commentedFor those who, like me, needs this functionality immediately, quick fix that adds "edit meta tags" permissions.
Comment #5
JThan commentedThanks for the diff. I also think that the Beta Version is buggy without this functionality.
Comment #6
danny englanderI just tried #4 above and it did create a new permission but the permission is not honored. A regular authenticated user can still see the meta tags fieldset even though they do not have any permission.
Comment #7
gleich commentedhighrockmedia, are you sure your 'authenticated user' role has neither 'administer meta tags' nor 'edit meta tags' permission?
Comment #8
danny englanderGleich, quite sure. I ended up creating a solution here:
http://drupal.org/node/912254#comment-3450290
Slightly different issue but related.
Comment #9
1mundus commentedIs there a chance that this bug will be fixed in 1.x stable version? I found a solution here:
http://drupal.org/node/823982
but it's actually a patch and this should be in 'core'.
Comment #10
xjmTracking.
Comment #11
xjmThis is a dup of #823982: Expand the Nodewords permissions to cover more granularity.