Bug #14249


Loom Embed Issue

Added by Laurie Hurson about 2 years ago. Updated about 2 years ago.

Priority name:
Category name:
Target version:
Start date:
Due date:
% Done:


Estimated time:
Deployment actions:


Hi all,

Loom videos are working on the Commons but when you embed from the block editor + Firefox, you get an error message in the editor. In Chrome Password-protected videos appear protected in the editor and the correct password does not work. (Screenshots attached)

Important to note, this does not happen across all sites on the Commons.
Issue visible on: - 19 plugins installed -0 plugins installed

Issue not visible on:

In both cases If you publish the page or post, the video works, but this error message may cause confusion for users. Is this an user-generated or browser generated issue or an issue that the commons team can resolve? If user-generated, I could write some documentation to clear up confusion.

I don't know if this is pressing since Looms videos do work, but wanted to flag this irregular behavior.



Actions #1

Updated by Boone Gorges about 2 years ago

  • Status changed from New to Reporter Feedback

Thanks for the detailed report.

The fact that this happens on non-published content suggests to me that Loom needs to be able to access the URL of the embedding page. When you are in the Block editor, or when you're viewing a preview of an unpublished post, you are looking at a URL that is not publicly accessible, and thus not accessible to Loom. As such, I don't think there's anything that the Commons can do to prevent it.

The password issue appears to be closely related. When you submit a password from the Dashboard interface, Loom expects to be able to send back a success message, but it can't because of the unpublished nature of the WP post.

I'd suggest that this limitation be outlined in the documentation about Loom embedding on the Commons.

Actions #2

Updated by Laurie Hurson about 2 years ago

Thanks for looking into this Boone. Your explanation of draft page and not-yet-live/public url causing the error makes sense.

I have a bunch of documentation to write so I will add this to my list.

Thank you!

Actions #3

Updated by Boone Gorges about 2 years ago

  • Status changed from Reporter Feedback to Resolved
  • Target version set to Not tracked

Thanks, Laurie!


Also available in: Atom PDF