unmerge css and js files on magento admin back-end

unmerge css and js files on magento admin back-end

October 13, 2026 · Illustrated author avatarBy Stefan Bogdanescu
unmerge css and js files on magento admin back-end

Troubleshooting CSS/JS Merging Issues in Magento Admin

If you’re experiencing CSS or JavaScript merging issues after pushing changes to your development environment in Magento, this guide will help you resolve the problem step-by-step.

Understanding the Merge Process

Firstly, let’s clarify why Magento is merging your CSS and JS files. This process helps improve performance by reducing the number of individual file requests on a page.

However, when your local environment has different versions or customizations than your live site, this merging can cause conflicts that make your changes invisible after deployment.

Locating the Merge Files

The merged CSS and JavaScript files are typically located in the pub/static directory. In most cases, you’ll see them prefixed with require- followed by a hash:

pub/static/adminhtml/Magento/backend/en_US/requirejs-config.js

Resolving Merge Conflicts

1. Disable Static Content Deployment

Before making any changes, it’s essential to disable the static content deployment process in your dev environment.

  • Log in to your Magento Admin.
  • Navigate to Stores > Configuration > Advanced > Developer.
  • Set “Static File Deploy” to “Disabled”.
  • Save the configuration.

2. Delete Existing Merge Files

Next, you need to manually delete the existing merged CSS and JavaScript files from the pub/static directory on your live server:

rm -rf pub/static/adminhtml/*

If you’re using a shared hosting environment, you may need to request this action from your hosting provider.

Remember: Always take a backup before performing these steps.

3. Update Your Magento Version

Ensure that the version of Magento running on both your local and live servers is identical. You can check the version number by looking at the footer of the Admin panel or using the following PHP code:

echo "Magento Version: ". Mage::getVersion();

If there’s a version mismatch, upgrade your live server to match your local environment.

4. Clear Cache and Re-index Data

After making these changes, don’t forget to clear Magento’s cache and re-index data:

rm -rf var/cache/*
php index.php --reindex

If you’re still experiencing issues, double-check that all third-party extensions (themes, plugins) are compatible with your current Magento version and have the same settings on both environments.

Conclusion

Resolving CSS/JS merging conflicts usually involves a combination of disabling static content deployment, manually deleting merged files from the pub/static directory, ensuring identical Magento versions across environments, and clearing cache.

Remember, this process should be done only in development or staging environments to avoid any potential issues on your live site. Always test changes thoroughly before deploying them to production.

For more advanced debugging techniques and best practices for managing CSS/JS files in Magento, I highly recommend checking out the [Magento 2 Development Guide] available at https://laravelcompany.com/magento-2-development-guide.

Performance Themes Admin Configuration

Our network