Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
In apparent disagreement with the direction of 8.x-2.x, I think Masquerade needs to be able to run as a production module. Currently, it's assigned to the "Development" package on the Extend page of modules. This is major not just in the re-naming, but in the concept of how to treat the access controls provided by the module.
It's a legitimate thing for customer service reps to be able to masquerade as users in certain roles, which isn't a development activity - it's a production one.
Comment | File | Size | Author |
---|---|---|---|
#1 | masquerade_development_module_list.jpg | 57.39 KB | deekayen |
Comments
Comment #1
deekayen CreditAttribution: deekayen commentedAdding a screenshot of what I'm talking about.
Comment #2
andypostAgree, 'development' is not a right place for module.
About approach I think we should introduce toolbar button to make module more friendly with none-devs
Comment #3
deekayen CreditAttribution: deekayen commentedI just removed the Development package until some other modules are updated and we can have the opportunity to talk about a better fit under a different heading.