I understand that for most Drupal users looking under "Content" to find "Add content" is natural. We've been doing it forever, and the "Add content" link is a LOCAL_ACTION on the find content page, so it seems natural to us.

However, for most of my administrators it's more natural to separate out the "Find/manage content" task from the "Add content" task. I've been doing this currently by moving the "Add content" menu link (and all it's children) up one level using hook_admin_menu_output_alter().

/**
 * Implements hook_admin_menu_output_alter().
 */
function mymodule_admin_menu_output_alter(&$content) {
  // Move add content to the top level.
  $add_content = $content['menu']['admin/content']['node/add'];
  unset($content['menu']['admin/content']['node/add']);
  $content['menu']['node/add'] = $add_content;
  $content['menu']['node/add']['#weight'] = -9;

  // Rename 'Content' to 'Find content'.
  $content['menu']['admin/content']['#title'] = t('Find content');
}

I've been doing this often enough that I thought I'd suggest this change here as well, since it might also benefit others.

Comments

Bao Truong’s picture

Thank you this works great!

hargobind’s picture

Thanks jen!

truls1502’s picture

Status: Active » Postponed (maintainer needs more info)
Issue tags: +postponed2w

I am sorry for no reply until now.

There are many issues regarding this module admin_menu which is a bit difficult for us to follow up since some of the issues might be already outdated, or is already fixed by the module or any other modules or itself core which means that the problem might no longer need to be fixed.

We can see that the issue has been created for a few years ago, I hope it is okay for you that I am postponing the issue, and give you around two weeks. If you still face the problem, could you tell us the step by step when until you get the error message or what is frustrated you, and a list of modules you are using related to admin_menu and a screenshot that might help us? So it makes us easier to reproduce your issue.

However, after two weeks with no feedback - we will close this issue. So in case, you noticed it after the issue is closed, do not hesitate to reopen it like and fill information which is mentioned above.

So before giving us a feedback, do you mind to test it again with our latest 7.x-3.x-dev?

Thank you for understanding! :)

truls1502’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)
Issue tags: -postponed2w

This issue has been automatically marked as closed because it has not had recent activity after the last post.

However, if you or someone is still facing the same issue as described to the issue, could you please to re-open the issue by changing the status of the issue, and add an explanation with more details which can help us to reproduce your situation.

Again, thank you for your contributions! :)