web_export_view Breaks native xls exportation about web HOT 7 CLOSED

Do you have any suspect?

from web.

The response is a 404 and the native exportation starts working again if you remove the ExcelExport inheritance, so I guess it has to do with the index redefinition.

from web.

When you have both services - /web/export/xls_view and /web/export/xls - pointing to the same index method, only /web/export/xls_view is in the map rules when looking for the handler, but I have yet to find why. If I rename index to anything else, both paths are present.

from web.

This might be the problem:

Each Rule object is instantiated with a string that represents a rule and an endpoint which will be the alias for what view the rule represents. Multiple rules can have the same endpoint, but should have different arguments to allow URL construction.

from web.

I see. Can we use the same service name for both things?

from web.

I think we can't, but I haven't seen any drawback to renaming the method. Both native and view exportation work when you rename it.

from web.

OK, let's see if there is any problem in the review process that we haven't seen.

from web.