Posted by subnet_rx on August 13, 2010 at 6:46pm
5 followers
| Project: | OG Menu |
| Version: | 6.x-2.4 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
I created two menus for a group. I ended up not needing the first one (default menu), so I went into the menu system and deleted it. Now, when I try to edit the second menu, I get this error:
The menu name cannot begin with "menu-".
Comments
#1
The patch from #754900: OG Menu names that start with menu- don't get associated with the group was a bad idea.
Here is a patch that should solve this issue while allowing to create menu beginning with "menu-".
#2
Thanks jide, after looking through the issues here, I assumed it had something to do with the fix of that bug. Thanks again, this was really in the nick of time for this project that I'm working on. I haven't applied it yet, but I'll test today and report back any errors.
#3
The patch has been committed to CVS.
#4
Automatically closed -- issue fixed for 2 weeks with no activity.
#5
This bug has come up again on my site. I actually probably haven't used OG Menu since the 2.4 update, so I'm guessing that is what caused it since applying the patch fixed it for me.
#6
Version update, I'm using 2.4
#7
Was this patch taken back out of CVS? Because after upgrading to the latest version, I had to reapply the patch to fix my problem.
#8
The error goes further then the described
I applied the patch and try to delete and now it says:
It does not allow me to ename the menu in order to make it shorter. This should be an error message before you create the menu, not after it is already created.
#9
Sorry everyone for not being very active lately. I will have a look at recent issues. Something went wrong with CVS releases I guess, those issues should have been fixed, I'll have a look at this soon.
#10
Running into this issue here, too... won't let me edit or delete any menus used by OG Menu module.
#11
bump
The 27 character bug is a Drupal core bug reported here and fixed in the dev version. Release 6.21 should have it fixed. That would mean that the proposed patch here is valid and fixing the other issue. Please apply and release.