Bug #99501
Updated by Georg Ringer almost 2 years ago
If an extension provides multiple plugins allowing the same action, an exception is thrown <pre> There is more than one plugin that can handle this request (Extension: "News", Controller: "News", action: "list"). Please specify "pluginName" argument </pre> Especially with the drop of switchablecontrolleractions, extensions like news split the features into various plugins. In this usecase there are 2 plugins using the same action @list@. To avoid issues with the plugin namespace in the request all plugins share the same namespace using <pre> plugin { tx_news_newsliststicky.view.pluginNamespace = tx_news_pi1 tx_news_newsdetail.view.pluginNamespace = tx_news_pi1 tx_news_newsselectedlist.view.pluginNamespace = tx_news_pi1 tx_news_newsdatemenu.view.pluginNamespace = tx_news_pi1 tx_news_categorylist.view.pluginNamespace = tx_news_pi1 tx_news_newssearchform.view.pluginNamespace = tx_news_pi1 tx_news_newssearchresult.view.pluginNamespace = tx_news_pi1 tx_news_taglist.view.pluginNamespace = tx_news_pi1 } </pre> Having now a datemenu with a template part like <pre> <f:link.action action="list" pageUid="{listPid}" arguments="{overwriteDemand:{year: year, month: month}}"> <f:translate key="month.{month}" /> {year} </f:link.action> </pre> it is up to the editor which plugin will handle the list action. I propose removing the exception. issues has been derived from https://github.com/georgringer/news/pull/1982 exception