Skip to main content
Magento

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • One subtle difference I think might be in how permissions are handled. I believe the M1 approach would only check on the new controller. Whereas with the above the plugin doing the authentication would still execute (ie if you don't have access to ModuleA you also don't have access to ModuleB). Commented May 18, 2017 at 22:13
  • you would also potentially disable plugins on the original controller action if you implement this plugin without calling the original method, which would be especially problematic to 3rd patry vendors Commented May 18, 2017 at 22:24
  • on the other hand, this might be exactly what you want in most cases when overriding controller actions. In a beautiful future maybe, the core controllers only execute functionality of models and you can just recompose them Commented May 18, 2017 at 22:30
  • Will need to consider layout updates when doing this. Commented May 19, 2017 at 16:49