Closed (cannot reproduce)
Project:
Administration menu
Version:
7.x-3.0-rc4
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Apr 2013 at 09:20 UTC
Updated:
2 Nov 2018 at 20:50 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Anonymous (not verified) commentedI've run into this as well, with a broken favicon in the Home tab of the Admin menu. Not a show-stopper, but I don't like having broken things on sites!
I was able to add the "http:" to the URI by putting the following in template.php.
It seems to correct the URI, but still leaves me with a broken favicon!
If anyone has a solution to this, it would be appreciated!
Alan
Comment #2
sunFYI: http://www.paulirish.com/2010/the-protocol-relative-url/
Comment #3
Anonymous (not verified) commentedSun, thanks for this, which I think explains what the Admin Menu is doing.
I had a further look at the module and documentation and took the route it recommends, which is to manage the icon directly, which I did using:
along with the attached image that I dropped into my theme folder.
Job done, more learned and on with the work!
Alan
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! :)
Comment #5
truls1502This issue has been automatically marked as closed 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.