Closed (cannot reproduce)
Project:
Administration menu
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
15 Jun 2012 at 06:37 UTC
Updated:
2 Nov 2018 at 21:30 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
les limPatch attached.
Comment #2
mrharolda commentedThe proposed solution does not work: the $cid is created in at least 2 places, and the call to domain_get_domain() will result in fatal errors on sites without the Domain Access module enabled.
I'll try to create a working patch today. Or something like that ;)
Comment #3
mrharolda commentedHere ya go!
I've recreated the patch above; this time with no direct Domains support, as that is a task for the Domain Access module, or you can implement the following code yourself:
Comment #4
les lim@MrHaroldA: That domain code was part of the api.php documentation file, as an example implementation of the new hook. I think the patch still needs some kind of example hook there.
Comment #5
mrharolda commentedAh! That explains why the tests didn't fail ;)
Comment #6
greg__ commentedI tested the patch and it works for me.
I had the same issue with cache between domain so I did use the hook exemple in #3.
Thanks
Comment #7
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 #8
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! :)