Home Magento 1.9.x - 404 Errors on Prod Server But Not On Local Dev Machine
Reply: 0

Magento 1.9.x - 404 Errors on Prod Server But Not On Local Dev Machine

user10201
1#
user10201 Published in September 21, 2018, 2:20 am

dealing with a strange issue here.

We've updated a Magento installation from 1.9.0.1 to 1.9.3.6. Had to re-code a custom module. Everything is working just fine on our local dev machines, which are a clone of the production server:

Nginx, PHP 5.6.30, MySQL

When we push the revision to production, everything works just fine, the admin panel shows Magento 1.9.3.6 but this one custom module (which modifies the admin customer detail view) throws a 404 error once a form is submitted.

All of this works perfectly fine on our local dev.

We've deleted the cache, re-indexed all data and triple checked that the code was transferred correctly. Everything matches the local dev but the custom module throws a 404 error on the prod server.

My questions:

(1) Any idea what is going on here ?

(2) Since the 404 Magento error page does not state any useful debug information, how can we debug the routing on the prod server ?

Thank you for your kind help !

controller class located at \app\code\local\Test\CustomCustomerFields\controllers\Adminhtml\CustomCustomerFields\IndexController.php:

class Test_CustomCustomerFields_Adminhtml_CustomCustomerFields_IndexController extends Mage_Adminhtml_Controller_Action {}

module config.xml:

...
<admin>
    <routers>
        <adminhtml>
          <args>
              <modules>
                  <customcustomerfields before="Mage_Adminhtml">Test_CustomCustomerFields_Adminhtml</customcustomerfields>
              </modules>
          </args>
        </adminhtml>
    </routers>
</admin>
...
share|improve this question
  • check namespace and lower and upper case problem and if possible show me the xml and controller class – faizanbeg Jan 16 at 5:42
  • any suggestion from the browser inspector about the request relative to the module? Maybe you've forgot to change some base url while transferring the module from dev to prod. Have a look to the core_config_data table. check also the namespace in the controllers as already suggested. – sissy Jan 16 at 9:03
  • @ sissy: the base url in the core_config_data table is correct, otherwise the entire prod site would not work. @ faizanberg: could you elaborate on the lower/upper case problem ? Are you referring to the Controller class name ? that one is correct, otherwise it would not work on the dev stage. Thanks !!! – mike Jan 16 at 12:42
  • I've added the controller class name as well as excerpt from config.xml file. Thanks. – mike Jan 16 at 13:06
  • check the url of the form or share the code with me its easy to debug – faizanbeg Jan 18 at 14:10

2 Answers 2

active oldest votes
up vote 0 down vote
You need to login account before you can post.

About| Privacy statement| Terms of Service| Advertising| Contact us| Help| Sitemap|
Processed in 0.330919 second(s) , Gzip On .

© 2016 Powered by mzan.com design MATCHINFO