Cannot edit categories in Magento after updating to 1.7

Cannot edit categories in Magento after updating to 1.7

September 25, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Cannot edit categories in Magento after updating to 1.7

[Blog Post]

Solving AJAX Category Editing Issues After Magento 1.7 Update

As a Magento developer, you’re likely to encounter technical snags after updating your e-commerce platform. One common issue that crops up post-Magento 1.7 update is the inability to edit categories due to broken AJAX POST URLs.

Identifying the Problem with AJAX URLs

Your local development environment might work smoothly, with AJAX calls functioning without a hitch:

http://local.my-domain.de/index.php/admin/catalog_category/edit/key/fcc2335e931e8ec4236be7da67156087/id/7/?isAjax=true

However, upon deploying to the production server, you may observe a disturbing pattern:

http://my-domain.de/index.php/admin/catalog_category/edit/key/1ac1f1e5f75e665a2fd06eca4569d662/?admin%2Fcatalog_category%2Findex%2Fkey%2F1ed297c236a0c9df5530952aaf7e0618%2F=id/7/&isAjax=true

The key field is getting encoded incorrectly, leading to a 404 Not Found error and rendering the category editing functionality useless.

Understanding the Root Cause

Magento 1.7 introduced several core improvements, including enhanced security measures around URL encoding. Unfortunately, this update also led to unintended consequences—specifically, incorrect encoding of complex URLs containing special characters or spaces.

Resolving the Broken AJAX Calls

To fix this issue, you’ll need to adjust your application’s configuration and potentially modify some core files. Here are two common approaches:

1. Adjusting the Admin Router Configuration

Open your app/code/core/Mage/Adminhtml/controllers/Catalog/CategoryController.php file and locate the _initAction() method around line 46. Modify the $request->setQuery() section to include a space between key parameters, like so:

$request->setQuery('id', $this->getRequest()->getParam('id'));
$request->setQuery('key', trim($this->getRequest()->getParam('key')));

This adjustment ensures that the keys are properly encoded and transmitted.

2. Updating the Mage_Core_Controller_Varien_Router_Standard Class

If the above method doesn’t work, you may need to update your core Mage_Core_Controller_Varien_Router_Standard class. Open the file located at app/code/core/Mage/Core/controllers/Router/Standard.php and locate the match() method around line 310.

Update the $request->setPathInfo() section as follows:

$request->setPathInfo($path);

The original code includes a space that’s causing the incorrect encoding. This correction ensures that the path is correctly set without any additional spaces.

Conclusion

Ensuring proper URL encoding is crucial for maintaining smooth functionality in your Magento e-commerce platform, particularly after major updates like version 1.7. By understanding the root cause of broken AJAX calls and implementing the necessary configuration adjustments or core file modifications, you can restore the category editing capabilities on your production server.

Remember to always backup your files before making any changes to the core codebase. If you’re unsure about the technicalities involved, consider reaching out to a professional Magento developer or seeking guidance from official support channels.

For more insights into Magento development best practices and advanced customization techniques, explore Laravel Company’s Magento resource center.

Magento 1 Catalog Security Themes

Our network