Edit URI for remote files

It looks like this is not currently supported. I started writing a patch for media_youtube, and then I realized that it was a lot more complicated due to the fact that media_internet is what handles this.

Here's a patch that adds this feature. From my limited testing, I've yet to see any ill effects.

Okay, so this actually adds a new file. Needs work.

Here's one that actually works.

and here's one with exception handling.

...and here's one that's actually diff'd against an UNPATCHED beta1. Testing is hard.

Here's an updated patch with better condition checking.

Nice work, leaning more towards putting this new functionality into the 7.x-3.x branch of media

Needs review+

looks good for both 7.x-2.x and 7.x-3.x

above patch caused regression in media_internet

Recent versions of media have resolved most of peoples concerns and is compatible with entity translation, multilingual and various advanced configurations. Due to the high volume of inactive and most often irrelevant issues we are Closing this as (outdated). If for whatever reason this issue is important to you AND you still have issues after checking the media recipe documentation, then let us know and we will review your concerns.

Otherwise, see the recipe documentation for how to configure media and for troubleshooting tips OR refer to the media_dev distribution if you want to see a working media setup.

As mentioned, feel free to make some noise in this issue if you still feel it is important to you or someone else.

Thanks,

Media team

I just had to replace a youtube video.
Currently you have to add a new file entity and replace it whereever u have used the old one. Thankfully there's the USAGE tab on every file, which shows you the places you have to edit.

For that use-case, it would be much easyer if the remote video's url was editable.
That would be the equivalent workflow as with local image-files, where you can replace the file.

I am surprised there are not more requests for this, but i would vote for re-opening the issue as it is a reasonable feature-request.