Closed (fixed)
Project:
Menu Settings per Content Type
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 Mar 2011 at 16:32 UTC
Updated:
25 Dec 2011 at 13:50 UTC
Jump to comment: Most recent file
Comments
Comment #1
vasikeComment #2
hixster commentedWhat additional info do you require?
Comment #3
vasike1. please try the dev version. maybe it's already solved.
2. what modules do you have installed?
Comment #4
vasikemoved to the new branch
Comment #5
hixster commentedI haven't experienced this issue again on my other sites so maybe close this for now. I'll reopen another ticket if it happens again.
Comment #6
vasikeok. thank you
Comment #7
imclean commentedI'm seeing a similar problem when creating new content. It can be attributed to the following piece of code:
Presumably
$form['menu']['parent']['#default_value']contains the value set at admin/build/menu/settings. The default menu must be set to a value so a menu will always appear.No menu is selected to display for the content type, but "Primary Links" is shown when editing and creating new content.
See #864582: Allow existing menu entry for a page to remain
Comment #8
imclean commentedThis patch fixes for me.
Comment #9
markwittens commentedI can confirm the patch in #8 works for me too.
Comment #10
vasikepatch commited http://drupalcode.org/project/ctm.git/commit/1142245
thanks. hope it works
Comment #11
imclean commentedShould do. As the other issue mentions, link_title is what the feature/fix is concerned with so it's probably best to check that directly. Also, the menu's #default_value isn't necessarily the item's menu.
Comment #12
vasikeis this solved after the commit?
Comment #13
imclean commentedWorks for me.
- When no menu is selected for the content type, the node create screen doesn't show the menu settings.
- When editing a node, the current menu settings are retained regardless of whether the menu is allowed or not.
Comment #14
s.daniel commentedDoes not work for me. (using dev version of nov 5th). The default menu set at /admin/build/menu/settings still shows up.
cleared the cache & re-saved every setting. Logged in as uid 3.
edit: After downgrading to 1.1. and reloading the old database the problem remains. Also after uninstalling and reinstalling + resetting the config.
Comment #15
renenee commentedSubscribing. I'm on the latest dev branch from 11/5. I have a content type with all menus disabled, yet they are all still available. I have also disabled Menu Admin per Menu in case of a conflict.
I am still receiving all options in the Menu Settings for this content type.
Also, I have tested making one menu available, and all menu options are available in the Menu Settings for this content type.
Comment #16
imclean commented#14 and #15, make sure you delete the old module before installing the latest dev.
Do you still see unchecked menus when creating new content or editing existing content? When editing content, you'll need to clear the "Menu link title" field, save the content, then click edit again to see the changes.
If none of the above solve it for you, could you check on a fresh install of Drupal.
Comment #17
s.daniel commentedThank you for your response!
I found my mistake and it works now, both with new nodes and existing ones using the latest dev.
The problem was that I had one version of ctm in the sites/all/modules and another one in the sites/default/modules folder. Probably because a drush command didn't work the way I was expecting it to. Result was that when I uninstalled and reinstalled the module the old version of the module was still used.
Comment #18
renenee commentedI tried #16 and no luck. I suppose I'll try a new install of Drupal.
Comment #19
imclean commentedAlso make sure you're not logged in as user #1. Apparently this works differently to the previous version.
Comment #20
renenee commentedWell, there you go. Thanks, imclean. #19 worked.
Comment #21
vasike