When using the admin_views module, admin/content is over-written with a view and uses the 'views_access' method as an access callback.

migrate_ui uses the path 'admin/content/migrate' and doesn't specify the access callback, so it defaults to the menu item above it which uses 'views_access' and causes migrate_ui to always get access denied.

I think admin_views should probably be updated to provide provisions for modules that expect admin/content to be unmolested, but a fix can also be made here by adding 'access callback' => 'user_access'.

Comments

mas5d2’s picture

mikeryan’s picture

Status: Active » Needs review

Be sure to use the 'needs review' status when submitting a patch.

mikeryan’s picture

Status: Needs review » Fixed

Yes, we're passing the access arguments for user_access, so should be explicit that it is our access callback. Committed, thanks.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.