How to debug: use WeltPixel Debugger and fix Magento 2 extension conflicts

WeltPixel Debugger ships with every WeltPixel extension as part of the shared Backend package and works with all installed extensions—not just WeltPixel products. Its goal is to quickly surface potential conflicts so you can debug faster.

Why conflicts happen

When multiple third-party modules try to change the same Magento class or behavior (e.g., via di.xml preferences or plugins), one may override the other. This can break or change functionality in unexpected ways.

Find conflicting rewrites

Magento Admin → WeltPixel → Debugger → Rewrites

The Rewrites report highlights classes that are changed by more than one module—these are high-probability conflict areas.

If two extensions conflict (same class is rewritten)

Solution 1 — Disable one module and retest

Quickly isolate the culprit by disabling a module, then verify the storefront/admin behavior.

# Disable a module and flush cache
php bin/magento module:disable Vendor_Module
php bin/magento cache:flush

# Re-enable if needed, then upgrade and flush
php bin/magento module:enable Vendor_Module
php bin/magento setup:upgrade
php bin/magento cache:flush

Solution 2 — Debug with a clear target

Use the Rewrites report to pinpoint the exact class/area that both modules touch. Typical next steps for a developer include:

• Reviewing di.xml preferences for duplicate class preferences.
• Auditing plugins (before/around/after + sortOrder) that target the same method.
• Consolidating logic into a compatibility module (preferred) rather than editing vendor code.

Verify you’re on the latest WeltPixel version

We constantly align our modules with new Magento releases. Running an older extension on a newer Magento version can cause issues.

Magento Admin → WeltPixel → Debugger → Extension Version

Note: A module tagged “Theme module” is part of the Pearl Theme. Removing or disabling it will break theme functionality. Other WeltPixel modules can be disabled without impacting the theme itself.

Quick tips

• After enabling/disabling modules in production mode, recompile if necessary:

  php bin/magento setup:di:compile
  php bin/magento cache:flush

• Avoid editing vendor code directly; create a small compatibility module to adjust preferences/plugins or sortOrder.

Updated on: 17/09/2025