using admin menu, content types are quickly accessibly using admin menu: for each content type you can directly access edit, delete, manage fields & display links.

it would be great if we had similar options for entity api dependent modules like field_collection and profile2 in order to directly access "manage fields" and other options.

Comments

fago’s picture

fago
Primary language German
Location Vienna
CreditAttribution: fago commented
Project: Entity API » Administration menu
Version: 7.x-1.x-dev » 7.x-3.x-dev
Component: Code - misc » Code

I had a look at the generated menu items and compared them to the content type items. I figured out the default local task for the listing was missing (local actions are local tasks too!). I've committed this fix.

However, still the individual profile types don't appear as menu item in admin-menu. Anything that's required from the admin_menu side to achieve that?

sun’s picture

sun
Primary language German
Location Karlsruhe
CreditAttribution: sun commented

Yes, the dynamic items are produced by hook_admin_menu_map(). Implementations for core modules as well as Views are contained in admin_menu.map.inc.

I'm not sure how many implementations of that hook are around in the wild, so in turn, I'm not sure whether we want to add the implementation into admin_menu or profile2.

That said, this would be the first fieldable contrib entity, and I almost guess that we'd also have to do something about field_ui_admin_menu_map() to expose the sub-items of Field UI.

truls1502’s picture

truls1502
he/him
Primary language Norwegian Bokmål
CreditAttribution: truls1502 as a volunteer and at SignWo AS commented
Issue summary: View changes
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

truls1502
he/him
Primary language Norwegian Bokmål
CreditAttribution: truls1502 as a volunteer and at SignWo AS commented
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! :)