How to Fix Magento 2 Autoload Error Caused by WeltPixel Backend Module Conflict When Installing GA4 PRO
When installing the WeltPixel Google Analytics 4 (GA4) PRO extension on a Magento 2 instance that already uses older WeltPixel modules (e.g., Pearl Theme or other extensions), you may encounter an autoload error related to the shared Backend module. This guide outlines how to resolve such conflicts to ensure successful installation and integration.
Understanding the Conflict and Autoload Error
All WeltPixel modules rely on a shared Backend module to provide administrative functionality within the Magento Admin. This shared module must only exist in one location to avoid autoloading errors, typically triggered when Magento detects duplicate modules in both app/code and vendor directories.
Locations where the module might be installed:
- Manual Installation: app/code/WeltPixel/Backend
- Composer Installation: vendor/weltpixel/m2-weltpixel-backend
Magento does not allow the same module to exist in both locations simultaneously, which leads to an autoload error.
Common Scenario
If your Magento store uses older WeltPixel extensions installed manually in app/code, and you’re trying to install GA4 PRO via Composer, you may receive an autoload error due to the Backend module being defined in two places.
Solution: keep the shared Backend module in Composer only
Composer is the only supported installation method, and GA4 PRO is not provided as a ZIP download.
- Remove the manually installed Backend module:
rm -rf app/code/WeltPixel/Backend - Install GA4 PRO with the Composer commands shown under My Products → Enable Composer at account.weltpixel.com, then run
php bin/magento setup:upgrade,php bin/magento setup:di:compileandphp bin/magento cache:flush.
Other WeltPixel modules still in app/code don't conflict with GA4 PRO, but migrate them to Composer as well so they stay updatable (see Migrating from manual SSH installation to Composer installation).
Updated on: 20/11/2026
Thank you!