Hello just discovered this when trying to install the analytics plugin.
This breaks both Merchello and Analytics.
Maybe plugin controllers should have some kind of prefix convention to prevent this happening?
An error has occurred.
Multiple types were found that match the controller named 'SettingsApi'. This can happen if the route that services this request ('umbraco/backoffice/Analytics/SettingsApi/{action}/{id}') found multiple controllers defined with the same name but differing namespaces, which is not supported.The request for 'SettingsApi' has found the following matching controllers:Analytics.Controllers.SettingsApiControllerMerchello.Web.Editors.SettingsApiController System.InvalidOperationException at System.Web.Http.Dispatcher.DefaultHttpControllerSelector.SelectController(HttpRequestMessage request) at System.Web.Http.Dispatcher.HttpControllerDispatcher.SendAsyncInternal(HttpRequestMessage request, CancellationToken cancellationToken) at System.Web.Http.Dispatcher.HttpControllerDispatcher.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
This happens because both me & Merchello have a controller called SettingsApi which I would say is a fairly common controller name for most package developers.
An issue was raised and this has been solved by the core team in Umbraco 7.1.5
Its a bit of debate if package developers should be making controller names a bit more unique to avoid this, but now you know why this has happened and a fix is available.
Error when using version 1.02 togheter with Merchello 1.3
An error has occurred.Multiple types were found that match the controller named 'SettingsApi'. This can happen if the route that services this request ('umbraco/backoffice/Analytics/SettingsApi/{action}/{id}') found multiple controllers defined with the same name but differing namespaces, which is not supported.The request for 'SettingsApi' has found the following matching controllers:Analytics.Controllers.SettingsApiControllerMerchello.Web.Editors.SettingsApiControllerSystem.InvalidOperationExceptionat System.Web.Http.Dispatcher.DefaultHttpControllerSelector.SelectController(HttpRequestMessage request) at System.Web.Http.Dispatcher.HttpControllerDispatcher.SendAsyncInternal(HttpRequestMessage request, CancellationToken cancellationToken) at System.Web.Http.Dispatcher.HttpControllerDispatcher.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)This happens because both me & Merchello have a controller called SettingsApi which I would say is a fairly common controller name for most package developers. An issue was raised and this has been solved by the core team in Umbraco 7.1.5
http://issues.umbraco.org/issue/U4-5151
Its a bit of debate if package developers should be making controller names a bit more unique to avoid this, but now you know why this has happened and a fix is available.
Many Thanks,
Warren :)
is working on a reply...