Closed (cannot reproduce)
Project:
Administration menu
Version:
7.x-3.0-rc3
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 May 2012 at 10:03 UTC
Updated:
2 Nov 2018 at 20:44 UTC
Jump to comment: Most recent
Comments
Comment #1
Tom Metz commentedHaving the same problem. Seemed to begin when I tried to install the weights module, things broke. I've uninstalled both the weight module and the admin menu but am still having it in Chrome. Not in Firefox though or IE.
Drupal 7.14
Admin Menu 7.x-3.0-rc3
Weight 7.x-2.0
Comment #2
todd zebert commentedwas having the same problem in Chrome and disabling 7.x-3.0-rc3 restored Row Weights, collapsible areas, and possibly other UI effects.
Comment #3
daniel wentsch commentedI haven't exeperienced the issue anymore for quite a while, i.g. with Admin Menu 7.x-3.0-rc1 and Chrome 22.0.1229.79 m
Comment #4
truls1502I am sorry for no reply until now.
There are many issues regarding this module admin_menu which is a bit difficult for us to follow up since some of the issues might be already outdated, or is already fixed by the module or any other modules or itself core which means that the problem might no longer need to be fixed.
We can see that the issue has been created for a few years ago, I hope it is okay for you that I am postponing the issue, and give you around two weeks. If you still face the problem, could you tell us the step by step when until you get the error message or what is frustrated you, and a list of modules you are using related to admin_menu and a screenshot that might help us? So it makes us easier to reproduce your issue.
However, after two weeks with no feedback - we will close this issue. So in case, you noticed it after the issue is closed, do not hesitate to reopen it like and fill information which is mentioned above.
So before giving us a feedback, do you mind to test it again with our latest 7.x-3.x-dev?
Thank you for understanding! :)
=====
Maybe it is fixed with a newer version of the Chrome browser?
Comment #5
truls1502This issue has been automatically marked as closed (cannot reproduce) because it has not had recent activity after the last post.
However, if you or someone is still facing the same issue as described to the issue, could you please to re-open the issue by changing the status of the issue, and add an explanation with more details which can help us to reproduce your situation.
Again, thank you for your contributions.