# Summary
This module enables you to make Menu Settings required on specific content types.
It forces a node from one or more content types to be included in the menu system before the content will be saved successfully. This can be useful in a number of situations, e.g. when using [menupath-raw] in the pathauto settings, which expects a node to live in the menu system. This module makes sure it does.
# Project URL
https://www.drupal.org/project/menu_force
# Where is the code?
https://github.com/akashjain132/menu_force/tree/8.x-1.x
# Estimated completion date
4st September 2016
# Dependencies
Menu UI Core module
# Who's doing the port?
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | port_menu_force_module-2794549-5.patch | 14.78 KB | BarisW |
Comments
Comment #2
perennial.sky commentedComment #3
perennial.sky commentedComment #4
BarisW commentedHi akashjain,
thanks a lot for this patch. It looks great, and I'm happy to commit this.
I've update the readme and help text to point the correct location of content types in D8.
There's one thing left; if a menu item is required, I would suggest to make toe 'Provide a menu link' checkbox read-only too.
Because now it is possible to uncheck this box, but then you cannot save the node anymore (very strange behavior).
But I'll commit the code first, this change can be added later.
Comment #5
BarisW commentedFor the record, here is the full patch.
Comment #7
BarisW commentedAnd here we go: https://www.drupal.org/project/menu_force/releases/8.x-1.0
Thanks a lot akashjain132 for writing the port.
I've also added you as co-maintainer of the module, in case you want to help out more often ;)
Comment #8
perennial.sky commentedHi BarisW,
Thank you for your time. Drupal 8 has the new feature that any required form element must be visible to user else it wouldn't allow the user to save the form. That's why I left it but now I think it is bad for the user experience so I fixed it.
I think now, I should change it's status to fixed.