Page builder error after Upgrade from Magento 2.3.3 to Magento 2.4.2 on admin

Page builder error after Upgrade from Magento 2.3.3 to Magento 2.4.2 on admin

September 30, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Page builder error after Upgrade from Magento 2.3.3 to Magento 2.4.2 on admin

Resolving Magento Page Builder Errors After Upgrading to Version 2.4.2

After upgrading your Magento installation from version 2.3.3 to 2.4.2, you may encounter errors while using the Page Builder feature in the admin panel of your e-commerce website. This article will guide you through identifying and resolving a common error that occurs when navigating to Content > Pages.

Understanding the Error

The error message typically appears in the browser console:

Could not load content for <a href="http://127.0.0.1/magento2.4.2/pub/static/version1618505838/adminhtml/Magento/backend/en_US/Magento_PageBuilder/js/content-type/slide/converter/attribute/overlay-color.js.map" rel="nofollow noreferrer">http://127.0.0.1/magento2.4.2/pub/static/version1618505838/adminhtml/Magento/backend/en_US/Magento_PageBuilder/js/content-type/slide/converter/attribute/overlay-color.js.map</a>: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

This indicates that the browser cannot find the specified JavaScript file (overlay-color.js.map) during the Page Builder initialization process.

Step-by-Step Resolution

To resolve this issue, follow these steps:

  1. Flush Magento Cache

    • Log in to your admin panel.
    • Navigate to System > Tools > Cache Management.
    • Select all cache types and click Flush Cache.
  2. Deploy Static Content

    • Go to System > Tools > Deployment.
    • Click on the Deploy button located under the “Deployment Action” section.
  3. Recompile Code

    • Navigate to System > Tools > Compilation.
    • If compilation is disabled, enable it and click Save Config.
    • Then, go back to the same page and click Compilation Status.
  4. Check Pub/Static Folder Permissions

    • Ensure that the pub/static folder has the correct permissions (775 or 755).
    • You can use the following command in SSH/SFTP:
    chmod -R 755 pub/static
    
  5. Clear Browser Cache and Cookies

    • Sometimes, browser caching might interfere with the updated static files.
    • Clear your browser cache and cookies.

Best Practices for Magento Upgrades

To prevent such issues in future upgrades:

Conclusion

Resolving this Page Builder error after upgrading to Magento 2.4.2 requires a combination of flushing caches, deploying static content, and ensuring proper folder permissions. If you’re still facing issues or have other questions regarding your e-commerce operations, feel free to explore our Magento consulting services at Laravel Company. We specialize in helping businesses optimize their Magento platforms for improved performance and security.

Remember, regular maintenance and staying updated with the latest Magento versions are key to a smooth e-commerce experience. Happy coding!

Magento 2 Cache Admin Deployment

Our network