Hello,
I am not sure when they appeared or why, but I have three "create content" menu items in the navigation menu. Each menu item brings up the "Create Content" page, but only one of them has a triangle icon next to it to indicate that it could be expanded.
I have tried clearing the menu cache (in fact all caches) and have reset all the menu items. I also have an issue where two recently modified content types (I changed the names of them) appear in the top level of the navigation menu rather than under the "create content menu.
I am not sure how to resolve to duplicate this. searching drupal.org has not given clues.
Cheers
Phil
Comments
Comment #1
mzwyssig CreditAttribution: mzwyssig commentedSame Issue here. I pulled the menu items out of the "Create Content" menu item to put them into another menu. And now I have about 10 of them.
And the page /node/add is empty.
Comment #2
kapow99504 CreditAttribution: kapow99504 commentedI'm having the same issue
Comment #3
chianti CreditAttribution: chianti commentedSame issue.
As normal my menu links have been turned into 'system links' (they have 'reset' rather than 'delete' next
to them in the list, and have a hyperlinked 'system' style url instead of a textbox that can be edited).
Same problem.
1)
I'm using an Artisteer template. Is anyone else using Artisteer?
If no, then we can eliminate that as a cause.
2)
Has anyone renamed the default navigation menu?
Mine is now called 'User Menu' and my user-name doesn't display when I'm logged in.
I don't remember how that happened: whether I edited that from within Drupal, whether it was done from
within Artisteer, or whether I edited the template files. It's been a while since I worked on this site.
I'm inclined to think it's an Artisteer thing, and probably isn't relevant to the problem.
3)
Has anyone renamed their content types? Especially the 'machine-name'?
When I did this, new menu links were created for the renamed content types without deleting the old ones.
These old menu items became the duplicate 'create content' links when I pressed the 'reset' links next to them.
I pressed 'reset' because I thought it might delete them.
4)
My 'node/add' page does list the content-types though; it's not blank like some of you describe.
5)
Is there something that we have we all got in common? What have you done or set-up that could affect the menu?
I have i18n installed and menu translations enabled.
I also have the Menu Trails module installed.
Can we narrow down what is causing this?
Cheers.
edit: I can't wait around for an answer because the work on this site needs to be finished in a few days. So, I went into the database using phpadmin, found the duplicate items in the menu table, changed their module type from 'system' to 'menu', which turned the 'reset' links into 'delete' links on the menu page, and so I could delete them from within Drupal. I have no idea whether that has solved the bug or not, or whether it will cause other problems, but it's academic to me until I need to edit/delete content-types again.
Comment #4
marcdecaluwe CreditAttribution: marcdecaluwe commentedSame issue here. I had the impression an extra menu-item is appearing when I remove a content-type (but not sure of this).
Maybe something related: when I remove a content-type, the menu-item node/add/content-type stays in place. I have to remove it manually. After that the extra node/add menu-item appears.
Comment #5
danielpd CreditAttribution: danielpd commentedsubscribe
Comment #6
chianti CreditAttribution: chianti commentedI think the trigger for this happening to me was editing the machine-name of a content-type.
There is a fix for these symptoms in this post:
http://drupal.org/node/149562#comment-1969614
Doing this will reset all your system menu-items, so you'll have to re-position them if you've moved them from their default positions or menus. Also read the suggestions of what you have to do after this, so that your menus are rebuilt.
Although there's a fix, this bug report should probably still stay open because the cause is obviously still present.
Comment #7
dddave CreditAttribution: dddave commentedre #6
I really think this is the same issue as in the issue you linked.
Comment #8
rggoode CreditAttribution: rggoode commentedsubscribe
Comment #9
Chimos CreditAttribution: Chimos commentedIn this thread:
https://drupal.org/node/149562#comment-1969614
The steps described in the post #25 by @hermes_costell solved this problem for me (Drupal 7.28).
IN ADDITION, at the end of these steps I needed to run cron and flush the cache.
Comment #10
pxljedi CreditAttribution: pxljedi commented#9 worked for me on a Drupal 6 to 7 upgrade. Thank YOU!