[development] Blocks and page context
E.J. Zufelt
lists at zufelt.ca
Fri Apr 23 21:30:08 UTC 2010
Good afternoon,
Thanks, this was quite helpful.
I notice that menu_get_item() will tell me if the current user can access the current menu item. Is there a simple method to test if user0 can access the current menu item? That is, regardless who the current user is, I would like to see if there is a function to let me know if user0 can access the current page, essentially a test to see if the current page is available to anonymous users or not.
Thanks again,
Everett Zufelt
http://zufelt.ca
Follow me on Twitter
http://twitter.com/ezufelt
View my LinkedIn Profile
http://www.linkedin.com/in/ezufelt
On 2010-04-23, at 12:03 PM, Daniel F. Kudwien wrote:
> $_GET['q'] holds the current, internal system path.
>
> menu_get_item() provides you the currently active menu router item.
>
> menu_get_object() provides you a dynamic argument context from the menu
> router item, if any.
> http://api.drupal.org/api/function/menu_get_object/6
>
> sun
>
> ________________________________
>
> From: development-bounces at drupal.org
> [mailto:development-bounces at drupal.org] On Behalf Of E.J. Zufelt
> Sent: Friday, April 23, 2010 4:49 PM
> To: development at drupal.org
> Subject: [development] Blocks and page context
>
>
> Good morning,
>
> I am building a module and invoking hook_block. I am wondering if
> there is a way for my block to gain some context about the page on which it
> will be rendered. Primarily I would like to know if my block can be aware
> of the URL of the page being displayed (not the http-requested URL in case
> they differ), and the access permissions of the page being displayed (not
> those of the block itself, or of the user accessing the block.
>
> Thanks,
>
>
>
> Everett Zufelt
>
> http://zufelt.ca
>
> Follow me on Twitter
> http://twitter.com/ezufelt
>
> View my LinkedIn Profile
> http://www.linkedin.com/in/ezufelt
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20100423/2f418537/attachment.html
More information about the development
mailing list