Project

General

Profile

Actions

Feature #67260

closed

Provide Start / Stop date for FAL entries

Added by Urs Braem almost 9 years ago. Updated over 1 year ago.

Status:
Rejected
Priority:
Could have
Assignee:
-
Category:
File Abstraction Layer (FAL)
Target version:
-
Start date:
2015-06-03
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

For almost all content elements in TYPO3 you can set start/stop dates in the "access" tab.
But not FAL entries (please close and correct me if I'm wrong).

This would not only be more consistent, but also quite useful:

A simple use case:
Display a list of PDFs in a directory. If a file is expired, don't display it. I understand the link would still be accessible if a public file storage is used, but at least it wouldn't be output. With a non-public storage, it would work flawlessly.

My actual use case:
we display job offerings on the website which expire after a certain amount of time. Each job offering consists of a news entry and a PDF.
The news entry will expire with it's stop date, but the PDF will stay sitting in it's folder. If the editor could set an expiry date when uploading the file, it would be marked as expired and could later on be purged with a scheduler job.

Actions #1

Updated by Frans Saris almost 9 years ago

  • Status changed from New to Needs Feedback

As FAL is only an abstraction of the file system a start and stop date wouldn't fit in this concept.

On a normal filesystem you also can not set a start and stop for files. You could enable these fields for sys_file_metadata and use that for your purpose. Not sure is we want/need to add this to the core.

Actions #2

Updated by Urs Braem almost 9 years ago

You could enable these fields for sys_file_metadata

You mean by adding them to the table with a custom extension?
Would the core respect the access dates automatically and not deliver files if the stop date has passed?

On a normal filesystem you also can not set a start and stop for files.

Yes, but that's why there is FAL: more flexibility and control over the files than on a normal file system (e.g. access restrictions)

Not sure is we want/need to add this to the core.

Ah I think it would be useful and consistent (TYPO3=set start/stop dates for anything).
I see my use case is a bit edgy though. Maybe some other opinions?

Cheers & Thanks

Actions #3

Updated by Alexander Opitz over 8 years ago

  • Category set to File Abstraction Layer (FAL)
  • Status changed from Needs Feedback to New

Implemented this a long time ago with 4.5 and DAM. The usage there was, that you can add a stop date to a file in a gallery. A right to use the images were payed for a given time so they needed to be disabled after the right of usage was over.

So maybe yes, a feature which have usage, but don't know if it may be possible to add this functionality as extension.

Actions #4

Updated by Alexander Opitz over 8 years ago

  • Target version changed from 7 LTS to 8 LTS
Actions #5

Updated by Adrian Dymorz over 7 years ago

I just received a request from a customer for this feature.

While looking for an extension which implements these fields, I did not find any (see https://typo3.org/extensions/repository/?q=fal&tx_solr%5Bpage%5D=1) but I found a stackoverflow question (http://stackoverflow.com/questions/30353522/how-do-i-add-publish-dates-to-uploaded-files-in-typo3).

Actions #6

Updated by Riccardo De Contardi about 7 years ago

  • Target version changed from 8 LTS to 9.0
Actions #7

Updated by Susanne Moog over 6 years ago

  • Target version deleted (9.0)
Actions #8

Updated by Christian Kuhn over 1 year ago

  • Status changed from New to Rejected

Hey. I hope it is ok to reject here for now: As mentioned by Frans, FAL is a layer on top of files. I don't think they should be timed records since that would lead to quite some headaches when dealing with re-indexing them. There seems to be rather little request for this feature, too, and if really needed, an extension could dig into details to see on how it turns out, first.

Actions

Also available in: Atom PDF