Closed (fixed)
Project:
MenuTree
Version:
6.x-1.2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
11 Apr 2008 at 19:13 UTC
Updated:
20 May 2008 at 18:11 UTC
I get an access denied message when trying to view a menu tree. As anonymous and as user #1. I just upgraded to Drupal 6.2
Comments
Comment #1
mgiffordGot the same problems.. Looking at the diff of 6.1->6.2 I think that the problem is around the access callbacks.. tried to change thhis quickly, but got the same results
41 'access callback' => 'menutree_user_access',
42 'access arguments' => array(1),
...
61 /**
62 * Access callback for menutree pages.
63 */
64 function menutree_user_access($account) {
65 // The visitor must be able to access the site's content.
66 return ( user_access('access content') && user_access('view site tree') );
67 }
Wanted to report this quickly.. Haven't looked into this in enough depth.
This is part of the form api changes that happened in the upgrade to 6.2:
http://drupal.org/node/244569
It does allow me to access it via the path menutree
However, I should be able to access it via the path
Unfortunately, I'm getting some menu warnings -- "warning: Invalid argument supplied for foreach()" due to some strings being sent for 'view site tree' rather than arrays.
I'm still not authorized to access the path menutree/primary-links mind you.
Mike
Comment #2
John Bryan commentedAlso suffering here. Was working before Drupal 6.2 upgrade was installed on a DEV site, so live site can not be upgraded until this is fixed or I remove menutree (can't leave broken functionality on the live site). I get the following when accessing it via a URL alias, even as user #1.
Oddly going to /menutree does work and shows the primary links menu, but /menutree/menu-[menu-name] does not.
Comment #3
Crell commentedHi folks. Yes, this was caused by the Drupal 6.2 menu permission changes. I just committed a fix. I will create a 1.3 release momentarily.
Cheers.
Comment #4
John Bryan commentedUpgrade fixed problem, thanks
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.