In particular, I'm working on a Magento site with a custom module that is only accessible if you include /index/
at the end of the module's frontend route. So the route is setup like this:
<frontend>
<routers>
<mycompany_mymodule>
<use>standard</use>
<args>
<module>Mycompany_Mymodule</module>
<frontName>shortname</frontName>
</args>
</mycompany_mymodule>
</routers>
</frontend>
On some servers and local installs of the site, example.com/shortname/
works. However, on others you get a 404 unless you go to example.com/shortname/index/
This leads me to a few questions:
- Any idea what causes the requirement for
/index/
in the route on some servers? - As a whole, are "index" as a default controller and "index" as a default action hard coded into Magento or is it something that can be customized per module?
- Particularly where in the code does Magento look for "index" controllers and actions?