Active
Project:
Menu clone
Version:
6.x-1.0-beta3
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Apr 2010 at 21:46 UTC
Updated:
23 Apr 2010 at 09:20 UTC
Jump to comment: Most recent file
Comments
Comment #1
malc0mn commentedI'll look into this further. The lost settings upon validation error will be reproducable and is definitely not good...
About the admin menu: was it the default admin menu you tried to clone? Are you using the Administration menu module as well?
What would help would be a look into your DB's menu_links table. Could you execute this:
SELECT * FROM menu_links WHERE menu_name = 'clone-admin-menu'or
SELECT * FROM menu_links WHERE menu_name = 'menu-clone-admin-menu'A 'menu-' prefix will always be added to the menu name, so it's probably the 2nd query...
Most likely deleting the clone will be safe, but to be sure, I would need to see the result of the query above...
Comment #2
Annakan commentedYou are right I use Administration menu and the menu I tried to clone was this one. I did not realize that Administration menu was creating a real menu since I activate it systematically I pretty much forget it is not a part of drupal core :).
I'll execute the queries ASAP.
Comment #3
Annakan commentedhere is attached the result of mysql> SELECT * FROM menu_links WHERE menu_name = 'menu-clone-admin-menu';
For informations
thanks a lot for your support.
Comment #4
malc0mn commentedFrom the dump.txt I can see it's safe to delete 'menu-clone-admin-menu'.
If you want to be absolutely sure you can:
DELETE FROM menu_links WHERE menu_name = 'menu-clone-admin-menu'I suspect the reason why you can't see the menu items is that a great deal of them are linked to the mlid '5751'. Could you do me a:
SELECT * FROM menu_links WHERE mlid = 5751and post the result? I bet 5751 does not belong to the 'menu-clone-admin-menu' menu, because it's not in the dump.txt :p
Could you give me the exact procedure you used to clone this menu, including any validation errors you encountered?
Before releasing the full rewrite of Menu Clone I had tested cloning the admin-menu several times, since it is the most challenging one ;-). I'm really curious to see what happenned here so I can fix it.
Comment #5
malc0mn commentedI reproduced the 'lost menu order after submit error' and found the following:
When dragging menu's below the ignore row, or dragging the ignore row itself, hidden weight fields are modified. When you submit the form and recieve a validation error, all fields you filled in are preserved! The problem with the draggable table is that you don't visually see this as such. The weight fields are OK, but the visual rendering is not.
That was the easy part, now for the solution. Ha, that's a whole different ballpark imho...
Comment #6
Annakan commentedSorry for the dealy in asnwering, busy days. :(
I'll look into that asap (the menu informations you asked)
Comment #7
malc0mn commentedNo problem man! I'm not in a hurry :-)
Comment #8
Annakan commentedSorry for the delay
SELECT * FROM menu_links WHERE mlid = 5751
gives
Comment #9
malc0mn commentedAs suspected, for some reason alot of items are linked to the source admin menu. I'll see if I can replicate this. As I said in #4, it's safe to delete the menu using Drupal, or the SQL I posted...
Thanks for the info!