Identifying Module Conflicts - mollie/magento2 GitHub Wiki

When troubleshooting issues where behavior differs between a clean Magento installation and a customized site, it’s often caused by third-party modules. To systematically identify the conflicting module, follow these steps:

  1. Prepare the Environment

    • Ensure you have access to disable/enable modules.
    • Keep the Mollie module (or the module you are testing) active.

  2. Disable Non-Magento and Hyvä Modules

    • php bin/magento module:disable $(php bin/magento module:status |grep -vE 'Magento|Mollie|Hyva|List|None|^$')
    • Disable all third-party (non-Magento) modules.
    • Confirm that only core Magento modules and the module under test are enabled.

  3. Test the Behavior

    • Reproduce the issue.
    • If the problem no longer occurs, proceed to the next step.

  4. Enable Modules in Batches

    • Re-enable a few (e.g., 3–5) third-party modules at a time.
    • Test the behavior after each batch.
    • If the problem does not appear, enable the next batch.

  5. Narrow Down the Conflict

    • When the issue reappears after enabling a batch, disable the last enabled batch.
    • Re-enable the modules one by one to identify the specific module causing the conflict.

  6. Document Your Findings

    • Once the conflicting module is identified, note it down along with the observed behavior.
    • If necessary, reach out to the module developer for further support.

Tip: Always clear cache and recompile (if necessary) after enabling or disabling modules to ensure changes are fully applied.