Follow-up to: #1836516: Port Masquerade to D8 and rewrite + simplify it into a new 2.x series

Problem

  • Anything beyond the most basic functionality has been moved into the separate masquerade_advanced.module.
  • The old code has been simply moved for the most part, and was not updated for recent API changes.
  • Some of its code still need to be upgraded for latest changes in D8.
  • Its additional functionality has no test coverage at all yet.

Notes

  • I'm not going to work on the masquerade_advanced.module, since my focus is entirely on making the main masquerade.module intelligent and smart. The main module's architectural design is documented in its README.txt. The concrete plans for the main module are documented in #1836516-32: Port Masquerade to D8 and rewrite + simplify it into a new 2.x series.
  • If the advanced module needs any API changes to make the advanced module work [better], let's ideally create separate issues to discuss.

Comments

andypost’s picture

andypost
he/him
Primary language Russian
commented
Issue summary: View changes

Commit 5e4c2cf03316d614f53336d0e567db17e317fe20 removed the module from 8.x-2.x branch

Suppose that module could be simply store allowed users in "user.data" service and implements hook_masquerade_access to add check for allowed UIDs

andypost’s picture

andypost
he/him
Primary language Russian
commented
Related issues: +#1949506: Allow the Admin masquerade search box to search on both email address and username., +#929250: Make username input field also accept user ID (in addition to name)
gagarine’s picture

gagarine commented
Status: Active » Closed (won't fix)

I guess this is very outdated.

gagarine’s picture

gagarine commented
Status: Closed (won't fix) » Closed (outdated)