A note regarding using Menu Settings per Content Type with this module:
Since the weight of Node Symlinks is set to 2, the Menu Settings per Content Type module is executed first. In instances where that module unsets the $form['menu'] element, Node Symlinks rebuilds it when it is executed farther down the process.
I've worked around this by setting the weight on Menu Settings per Content Type to 3 so that when the core menu element is dropped, the Node Symlinks component is already a part of it and is unset as well. I'm not really sure what is a good fix for this, given that Node Symlinks is purposefully weighted as 2, and I don't know what the bigger picture implications would be to the Menu Settings per Content Type project to have its weight set heavier by default.
Without a suggestion for a real fix, I guess my suggestion would be to document this behaviour as a "gotcha" with workaround instructions.
Comments
Comment #1
gooddesignusa commentedThank you. Changing the weight worked for me.
Comment #2
wojtha commentedThis is still issue for 6,x-1.0-beta3.
Fixed in current dev (check github for the latest dev release).
Update: Fixed in 6.x-1.0-beta4 release