This project is read-only.

Routes Stop Working When Upgrade to Newest Orchard Version

Topics: Troubleshooting
Jun 24, 2015 at 7:39 AM
Just short story here. I have hosted my Orchard site on and I used Orchard 1.7. Then I have recently upgraded a project from Orchard 1.7.2 to Orchard 1.9.

One of my modules in this project has a Path of Common defined in the module manifest.

This creates URLs along the lines of api/Common/Pipeline.

After upgrading to Orchard 1.9, all of the routes that use this path have stopped working; they simply resolve as a 404.

Changing the Path to something other than Common resolves the issue (albeit with different routes).

Has something changed between Orchard 1.7.2 and 1.9 that would prevent me from using the path Common in one of my own modules? Can I revert this behaviour so that I can keep my original routes?
Jun 24, 2015 at 6:09 PM
Not intentionally, you should file a bug if it's not already done.

One possibility is that you actually have a folder named api/common in your filesystem. Another reason would be that you have a module named "Common" in its manifest and the default built routes would then take over your custom ones.