Thanks, fixed in the development tree. The spam logs were requiring a nonexistent permission making them only accessible to UID 1. Check out the latest copy of the spam.module, then be sure your role has 'administer spam' permissions.
Download the -dev tarball. It is only updated once or twice a day, but enough time has gone by now that it includes the updates from yesterday.
(You can also manually apply the patch, by following my link above to the source change. Or you could check the module out from CVS. Both are documented on the Drupal.org web pages.)
Comments
Comment #1
jeremy commentedThanks, fixed in the development tree. The spam logs were requiring a nonexistent permission making them only accessible to UID 1. Check out the latest copy of the spam.module, then be sure your role has 'administer spam' permissions.
Comment #2
udijw commentedThanks Jeremy,
I'm a newbie at this, how do I get the latest copy of the spam.module?
Comment #3
jeremy commentedDownload the -dev tarball. It is only updated once or twice a day, but enough time has gone by now that it includes the updates from yesterday.
(You can also manually apply the patch, by following my link above to the source change. Or you could check the module out from CVS. Both are documented on the Drupal.org web pages.)
Comment #4
udijw commentedThanks
I fllowed the link and changed 4 lines to
'access' => user_access('administer spam'),and everything works as designedComment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.