Issue Feature Under Review Orphaned

#107120Why should we keep real files for online media?

Benni Mack 07/21/25, 16:44 updated 04/21/26, 11:23

Description

TYPO3 could actually just remove the need to store physical stub files for youtube or vimeo files?

Reviews 1

History 47

  1. Francois Suter commented <span data-processor="relativetime" data-value="2025-10-30T11:24:58+00:00" > 10/30/25, 11:24 </span>

    This would be a really great feature. Here are my thoughts, partly in answer to the questions in the commit message:

    Filelist module

    I’m not sure how the list is currently assembled, but we would get the list from the database, then check the corresponding folder for “physical” entries (to check if any is missing). For the virtual items, we could check for a 200 response, but that makes for a lot of request in list view, so maybe just display them as is (the information pop up could display issues; and of course the thumbnail generation would error too, but that’s cached, right?).

    About thumbnails, see “Rendering” below

    About actions and permissions: since every entry would be attached to a folder anyway, I don’t see a real issue about permissions. However some actions don’t make sense or need to be changed:

    • Edit: is just about metadata, no problem
    • Replace: this would mean changing the remote URL. The payload needs to be updated.
    • Rename: does not make sense and would not be available
    • Download: would need some disabling feature. Currently it seems to be active all the time, although trying to download a YouTube video fails unsurprisingly. Download might also need to be disabled depending on remote source.
    • Cut/Copy: no problems, just moves or copies the entry to another folder
    • Delete: would just delete the sys_file entry. The original source of a virtual entry cannot be deleted, as we do not interact deeply with remote sources in this case. This is only possible with a full FAL driver integration.

    Rendering

    We could have generic renderers, for example with images. All images can be handled in the same way, we don’t need a helper for each image type. What we need is the image processing service to be able to start from a remote image and not a local one. This can be used for both BE thumbnail and FE image view helper.

    Media payload

    Similar reflection as above. For example, for images, all we need is to store the URL of the image in the payload field. We don’t need any processing like extracting the YouTube code. Storing the URL would be the default behaviour.

    So I think we still need helpers (both for uploading and usage), but there would be generic ones for certain file types. Maybe this applies only to images. Would it make sense to reference remote text files? Or other types?