Problem/Motivation

Media items will not save after initial creation

Steps to reproduce

  1. Create a CF stream media item and save
  2. Edit the saved item, change the title and save
  3. " Only files with the following extensions are allowed: mp4 mkv mov avi flv ts tsv tsa mpg mpeg m2p ps mxf lxf gxf 3gp webm qt. "

Proposed resolution

Adjust the extended file field validation to account for a valid CF stream

Remaining tasks

User interface changes

API changes

Data model changes

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

fathershawn created an issue. See original summary.

fathershawn’s picture

fathershawn’s picture

Status: Active » Needs review
furamag’s picture

Tested and it works for me.

bmateus’s picture

Any news on when this is being released? I'm experiencing the same issue.

fathershawn’s picture

Assigned: fathershawn » Unassigned
ian.ssu’s picture

Status: Needs review » Reviewed & tested by the community

I tested the patch with 3.0.0-beta2 and it fixes the issue that blocked saving content with a Cloudflare Video field after the initial upload.

My test case used a Cloudflare Video field in a Block within Layout Builder. Before the patch, creating the block worked, but saving after edits threw the reported error. After applying the patch, I could save changes to the block without errors.

The code looks like a reasonable approach. It removes the file_extensions constraint when the current file is a Cloudflare Stream URI.

tim-diels’s picture

Version: 3.0.0-beta2 » 3.0.x-dev

Sorry for the very late follow up. This looks very good and will include it in the next release.

tim-diels’s picture

Status: Reviewed & tested by the community » Fixed

Thanks all for the work done!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.