Masquerade module support

Didn't this used to exist from one side or the other (under 6.x)?

(Note: devel switch may be more viable ... if one does not need fine-grained perms )

Devel switch already works, if you have admin_devel enabled. But it doesn't allow you to switch back from an unprivileged user, as masquerade does. That said, I guess it would be nice to also remove the devel switch option from admin menu if masquerade is found?

The first patch adds a submodule for masquerade support. Enable the submodule and you will get an embedded masquerade form with autosubmit in the administration menu.

I don't know if it is for everyone's use case. But I also added a check for the masquerade session so the admin menu will always get output no matter the users rights. Maybe that should belong in a setting.

The second patch comments out a few caching rules that don't allow for the user to switch with masquerade. I need some help figuring out how to make the masquerade form work with the admin menu's caching system.

Looks like I had wrong version of patches (without the autosubmit). Please test following patches.

I 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! :)

This 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! :)