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

WeltPixel Debugger is delivered with all our extensions as part of the Backend shared package and was developed in order to provide valuable insights about the 3rd party extensions installed on the store. It works with all installed extensions and is not limited to WeltPixel products.

Sometimes, when using extensions from different vendors, Magento classes are overwritten more than once by different extensions. This may cause conflicts and break desired functionality.

The debugger functionality points out the classes that are overwritten more than once by 3rd party extensions, as there is a high probability of conflicts in that code section. This should improve the debugging process by pointing the developer or store owner in the right direction. 

Go to WeltPixel > Debugger > Rewrites

- What to do if 2 extensions are conflicting because of rewriting the same classes?

Solution 1: The easiest approach is to disable one of the extensions and check the store functionality. You may find out that it's more convenient to remove the extension causing the conflict and install a different one. 

Solution 2: You may start the debugging process with your developer by having a clear idea which modules are conflicting and where to look for the issue. 

- Make sure to check the WeltPixel Extension version.

Also, make sure you are using latest version of the WeltPixel extension, we are constantly improving our products and aligning them with all new Magento releases. Using an older extension version with the newest Magento release may sometimes cause troubles due to the changes made to the Magento 2 core in each release. 

WeltPixel > Debugger > Extension Version

Note: The 'Theme module' tag means this module is part of Pearl Theme for Magento 2 and removing this module will break theme functionality. All other WeltPixel modules can be disabled without affecting theme functionality.