Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Bundle info has been moved to a new hook hook_entity_bundle_info()
and the menu_link entity type doesn't even need to explicitely declare any bundle at the moment.
Comment | File | Size | Author |
---|---|---|---|
#1 | 1937384.patch | 572 bytes | amateescu |
Comments
Comment #1
amateescu CreditAttribution: amateescu commentedAnd the patch.
Comment #2
swentel CreditAttribution: swentel commentedComment #3
amateescu CreditAttribution: amateescu commentedCan't get any 'quicker' fix than this :)
Comment #4
amateescu CreditAttribution: amateescu commentedSorry, x-post.
Comment #5
andypost+1 here and follow to issue #1966298: Introduce menu link bundles per menus
Comment #6
Gábor HojtsyWhere is this bundle defined then? I see user defines it with this hook, but no such hook for menu items? http://api.drupal.org/api/drupal/core%21includes%21entity.api.php/functi...
Comment #7
amateescu CreditAttribution: amateescu commentedIt's provided by default in entity_get_bundles().
Comment #8
Gábor HojtsyWhy do user module define it then?
Comment #9
webchickLooks like this still needs discussion.
Comment #10
Gábor HojtsyI've been responded to on IRC that people don't know either. However a module doing something relatively useless should not be a reason for this to do it too. One thing that user module does is it specifies a path for the account settings (as the bundle config path?) which is kind of odd. Although if that is useful for some UI interaction, then maybe menu module should do the same?
Comment #11
swentel CreditAttribution: swentel commentedThat path is used by Field UI so the 'Manage fields' and 'Manage Display' screens are placed correctly, so that's only usefull if your entity is fieldable.
Comment #12
Gábor HojtsyThanks!
Comment #13
webchickCommitted and pushed to 8.x. Thanks!