Tell me more ×
Stack Overflow is a question and answer site for professional and enthusiast programmers. It's 100% free, no registration required.
up vote 0 down vote favorite

I've successfully built my first full Orchard module. It's a module for generating an XML sitemap based on the available (published) content items that have the Autoroute part. Everything works like it's supposed to locally.

Now I tried to publish my website (ftp), but on the server the module doesn't seem to work. When I go to the sitemap.xml it results in an IIS 404 page (so not even an Orchard 404 page). So it seems the Route doesn't work.

The log files located in the App_Data folder are also empty.

Any ideas to why my module might not work? Could it have anything to do with the server configuration? My module contains little code and can be downloaded here: http://we.tl/w7S7A6ksJG

share|improve this question
When I was working on the module locally, I would also got "orchard-debug-2013.06.05.log" files, containing exceptions etc. Is there a way to get that debug information on the server? – Tst Jun 5 at 18:48
that should work on the server also. Please give details of setup. Managed server, Windows Azure Website, Windows Azure web role, etc. The normal reason for a 404 is a low-level error bombing out orchard before routing can take over. Does the site work before you deploy the new module? – Paul Devenney Jun 5 at 19:15
Are you sure the generated file is being created on the server at all? It may be due to apppool user not having proper permissions to store the file and the exception may be swallowed somewhere in the process. – Piotr Szmyd Jun 5 at 19:25
The site works fine, even when the module is installed everything is ok. Only the /sitemap.xml results in a 404 IIS error. I'm running the website on a Managed VPS. I believe it's running IIS 6.0, AspNet-Version: 4.0.30319, AspNetMvc-Version: 4.0. – Tst 2 days ago
It's typical to get 404s for example when the module failed to compile, so that's one thing to verify. Another reason may be a difference in web.config preventing the route from being served at all. Is the 404 looking like a IIS message or an ASP.NET error page? – Bertrand Le Roy yesterday
show 1 more comment

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.