In previous versions you needed to have the Webmaster status to see plugins and their configuration.
The intended behavior of this page is : You can activate or deactivate plugins only if you are Webmaster but as an admin you can edit the configuration of any plugin.
So we need to show plugins and specify to administrators that they must be Webmaster to activate/deactivate plugins + the UI has to follow this behavior by cancelling switch activation as admin.
Moreover, the API let us perform actions on plugins as administrator so we also need to check the status in the API method.
In previous versions you needed to have the Webmaster status to see plugins and their configuration.
The intended behavior of this page is : You can activate or deactivate plugins only if you are Webmaster but as an admin you can edit the configuration of any plugin.
So we need to show plugins and specify to administrators that they must be Webmaster to activate/deactivate plugins + the UI has to follow this behavior by cancelling switch activation as admin.
Moreover, the API let us perform actions on plugins as administrator so we also need to check the status in the API method.
<!-- github-sync-id:1016349500 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In previous versions you needed to have the Webmaster status to see plugins and their configuration.
The intended behavior of this page is : You can activate or deactivate plugins only if you are Webmaster but as an admin you can edit the configuration of any plugin.
So we need to show plugins and specify to administrators that they must be Webmaster to activate/deactivate plugins + the UI has to follow this behavior by cancelling switch activation as admin.
Moreover, the API let us perform actions on plugins as administrator so we also need to check the status in the API method.
Border effet in others pages example in edit album (switch btn broken)