Composer Won't Upgrade a Module That Has Moved to Open Source

Problem

Some WeltPixel extensions are eventually discontinued as commercial products and re-released as free, open-source modules. When this happens, the module is typically given a new module/package name and is maintained in a public source repository rather than through the original commercial Composer package.

If you try to upgrade an older installed version using the original package name, Composer will fail or refuse to pull the newer release. This is expected — from Composer's point of view, the old commercial package and the new open-source module are two different packages, so a normal composer update cannot bridge between them.

Solution

1. Confirm the module's current status. Check the product listing on the WeltPixel site or the module's release notes to see if it has been discontinued and re-released as an open-source module under a new name.

2. Remove the old version. Depending on how it was originally installed:

• If installed via Composer:

   composer remove weltpixel/<old-package-name>

• If installed manually, delete the corresponding folder under app/code/WeltPixel/.

3. Disable/clean up the old module registration if it's still listed:

 bin/magento module:disable WeltPixel_<OldModuleName>

4. Install the current open-source release. Open-source modules are generally distributed from WeltPixel's public source repositories rather than through the original Composer package. Download the latest release for the module and install it following the instructions included with that release (this is often a manual app/code install rather than a Composer package, since the module may no longer be published to a Composer registry).

5. Run the standard post-install commands:

 bin/magento setup:upgrade
 bin/magento setup:di:compile
 bin/magento setup:static-content:deploy -f
 bin/magento cache:flush

Verification

1. Run:

 bin/magento module:status | grep WeltPixel

Confirm the old module name is no longer listed and the new (open-source) module name appears and is enabled.

2. Check the module's version file or changelog to confirm it matches the latest available open-source release.

3. Load the storefront and confirm the feature previously provided by the module (e.g., lazy loading of images) still functions correctly, and check the browser console/logs for related errors.

Updated on: 18/09/2026