In 2989526 → the form widget for the element was changed from a standard select to a custom element. As part of this, the #options array key where the menu parent options were stored changed to #menu.
Other modules that interact with this element expect the values to be in the #options key. The one causing issues for me is menu_admin_per_menu, which checks whether there are any values in #options and, if not hides the menu link form.
I can work on a coded solution for this, but I'm wondering if you have any preference for how to handle this. Would it be best to change the element back to a standard select with an #options key or throw a copy of the #menu in there and mark it validated, or something else?
Fixed
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I have just saw the same issue in my project. It also happens with menu_admin_per_menu module. The patch fixes the problem and also seems to be logical. At least #default_value and #options should be back in the form element
Thanks for the contribution y'all! This is releasing as part of 2.0.0-rc2.
Automatically closed - issue fixed for 2 weeks with no activity.