Apr 06, 2016
Apr 22, 2016
Closed, Fixed and tested
Suggestion from EMVP:
Installing this however gives an error, more specifically that that the attribute routing is already configured. So am I missing something here or should the mapping of the httpattributes not be done in the forms api, as it is already done in the service api, on which it depends?
If I disable the mapping for the service api in the app settings, the error is gone and the mapping still done. Which is a fix, but I don't think I should have to?
I see the instruction to set "episerver:serviceapi:maphttpattributeroutes" to false. But why should I have to do that? The forms api depends on the service api, so the attribute routing would have been mapped already, right? There is no need for the forms api to do it as well? It might also cause a problem if other modules want to register attribute routing and you cannot disable it for the forms api as well?