Same problem arised me last

blueeye — Sun, 21 Mar 2010 16:56:01 +0000

Same problem arised me last week and I was searching for the issue but can't find it over internet. One of my friend gave me the same solution. Today while reading this post, I got the idea from where my friend got the idea

Had the same problem, and

jontanderson — Thu, 25 Feb 2010 12:49:46 +0000

Had the same problem, and have spent countless hours trying to find a solution. The one(s) presented here work! Its awesome!

Thanks so much!

Found it. It was the

davecoventry — Fri, 28 Aug 2009 21:45:35 +0000

Found it.

It was the hook_perm as you said:

<?php
function simpim_perm(){
    return array('access messages');
}
?>

Once I put that into my module, it showed up in the permissions page so I could click 'authenticated use' and it worked.

Sheesh!

I have been struggling with this for 4 weeks!

Bugger! I thought it was

davecoventry — Fri, 28 Aug 2009 16:49:13 +0000

Bugger!

I thought it was sorted, but it appears to only be sorted for the admin account. Ordinary users are still getting 403.

davecoventry

JeevesBond — Fri, 28 Aug 2009 06:53:21 +0000

davecoventry wrote:

JB,

Forgot to say thanks!

No manners, I'm afraid. :(

No worries. You're welcome.

So the string is actually a

JeevesBond — Fri, 28 Aug 2009 06:52:48 +0000

So the string is actually a space-separated array? Bizarre.

Nope.

It's just an array of arguments to pass to the access function. For example, you could use:

<?php
'access arguments' => array('kiss my arse'),
?>

As long as you define the permission in a hook_perm implementation, you'll be able to see it on the Administer -> User management -> Access control page.

Where do you get a listing for the valid values for this array?

Any strings are valid (see above), I made up the 'access messages' permission. Drupal builds the list of permissions automatically from every module's hook_perm, so you really can give it any values you want. Just remember to get Drupal to rebuild its cache by visiting Administer -> Site building -> Modules.

Go to: Administer -> User management -> Access control and you'll see your permission there.

I actually said to Heine that I thought that the 'access arguments' was a list of local parameters to be passed to the callback function and he didn't disabuse me of this.

It is! Check out user_access. The arguments in the access arguments array are handed to the user_access function.

JB, Forgot to say thanks! No

davecoventry — Thu, 27 Aug 2009 18:50:22 +0000

JB,

Forgot to say thanks!

No manners, I'm afraid.

JeevesBond wrote: Does that

davecoventry — Thu, 27 Aug 2009 06:06:45 +0000

JeevesBond wrote:

Does that make sense?

Not really.

So the string is actually a space-separated array? Bizarre.

Where do you get a listing for the valid values for this array?

I actually said to Heine that I thought that the 'access arguments' was a list of local parameters to be passed to the callback function and he didn't disabuse me of this. Even when I said that I didn't use it because I was reading the arguments from $_GET mechanism.

Also, I *was* testing from the admin account and it still gave me the 403.

As Heine said, rather

JeevesBond — Thu, 27 Aug 2009 02:29:07 +0000

As Heine said, rather tersely, it's a list of the permissions the user has to have before they can access the menu item. If you're testing this as the admin user you'll get a free pass, because you get a free pass for every permission. Try accessing that URL as an anonymous user, or user who doesn't have that permission and you'll see the access denied message.

Does that make sense?

Hey JB! It worked! How is

davecoventry — Wed, 26 Aug 2009 15:35:33 +0000

Hey JB!

It worked!

How is that possible?

What exactly does array('access messages') mean? Surely it's an array with one element which holds a string, but I can't see the relevance of that string.