Missing js vimeo library

[angelo983]

Preconditions and environment

• Magento 2.4.4
• Magento_PageBuilder enabled
• Js bundling enabled
• PHP 8.1
• Production mode

Steps to reproduce

• Load an extension that require vimeo as library;
• Create a block of this type with height bigger than viewport height, but not loading any video in content;
• Switch to production mode with active js minification.

Expected result

Div scrolling without problems

Actual result

Scrolling hangs while scrolling

Additional information

In console this error appears: /*****/ homepage:1 Refused to execute script from '/vimeoWrapper.min.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled. main.min.js:3 Error: Script error for "vimeoWrapper", needed by: Magento_PageBuilder/js/widget/video-background https://requirejs.org/docs/errors.html#scripterror at makeError (require.min.js:17:53) at HTMLScriptElement.onScriptError (require.min.js:117:697) require.min.js:127 GET /vimeoWrapper.min.js net::ERR_ABORTED 404

require.min.js:127 GET /vimeoWrapper.min.js net::ERR_ABORTED 404 /*****/

In /vendor/magento/module-page-builder/view/base/requirejs-config.js these resources are requested: 'Magento_PageBuilder/js/resource/vimeo/player': 'vimeo/player', 'Magento_PageBuilder/js/resource/vimeo/vimeo-wrapper': 'vimeo/vimeo-wrapper',

but in /vendor/magento/module-page-builder/view/base/web/js/resource vimeo folder is not present.

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [X] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [X] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @angelo983. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

  :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant[bot]]

Hi @engcom-November. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

Hi @angelo983 , Thank you for reporting and collaboration. Verified the issue on Magento 2.4-develop instance but unable to reproduce the issue on configuring product videos in both ways as mentioned below: Steps:

1. Enabled Production mode.
2. Configured Vimeo video for a product by configuring in both ways. 1. As per Magento docs and 2. devdocs
3. Enabled JS bundling as per Magento devdocs
4. Access front end - Product details page - No issue and no errors in console observed.

Kindly confirm if you are using any 3rd party extensions / modules enabled that's causing the issue and recheck on Magento 2.4-develop instance as it is the upcoming 2.4.x release and provide missing configuration details if any if the issue is still reproducible. Thank you.

[angelo983]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @angelo983. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @angelo983, here is your Magento Instance: https://b3828b078c2db12ee7e2acfd1153d78e.instances.magento-community.engineering Admin access: https://b3828b078c2db12ee7e2acfd1153d78e.instances.magento-community.engineering/admin_edca Login: 0c31daf8 Password: fdcc58000485

[johncarlson21]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @johncarlson21. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @johncarlson21, here is your Magento Instance: https://b3828b078c2db12ee7e2acfd1153d78e.instances.magento-community.engineering Admin access: https://b3828b078c2db12ee7e2acfd1153d78e.instances.magento-community.engineering/admin_4ede Login: 20d28132 Password: d0e4de08c04e

[loic-paquin]

I had the same issue, you probably ran a composer update after the release of 2.4.5. It is caused by the version 2.2.3 of the PageBuilder module. Also my pageBuilder in the Back Office was unusable ( Sliders were not loading).

You can check the PageBuilder version in this file : vendor/magento/module-page-builder/composer.json

You can resolve the issue by typing the command : composer require magento/module-page-builder:2.2.2 After this, as usual, compile + deploy static + clean cache.

[engcom-November]

Hi @loic-paquin , Thank you for the response. There is an ongoing current Page builder issue which is confirmed and being tracked here. Please move onto this issue for latest updates / solutions on the same. As the issue not reproducible on clean 2.4develop instance, we are closing this issue. Kindly reopen / create new issue if you are still facing any issues. Thank you.

[angelo983]

Updates: DevTools failed to load source map: Could not load content for https://5a6e47f9b7eaa11ced36627e0bf2d9f2.instances.magento-community.engineering/static/version1667504227/frontend/Magento/luma/en_US/vimeo/player.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

https://5a6e47f9b7eaa11ced36627e0bf2d9f2.instances.magento-community.engineering/set-of-sprite-yoga-straps.html

You can see this error in a fresh magento 2.4.x develop instance in a grouped product page