Bug #62537
closedFileadmin meta data in workspace (FAL)
0%
Description
If a user uploads a file to the fileadmin he can provide some meta data. The file is immediately LIVE, because the fileadmin is not part of the workspace management in TYPO3.
The problem occurs, when using a workspace: There is no possibility for users to see the meta data in the workspaces module and to publish it (we tested it with full group rights). This means that the file is live but without meta data. Only TYPO3 admins can publish the meta data.
This leads to another problem: If a user integrates the uploaded file in a content element in the workflow and sees the metadata there (grey letters) and does not overwrite it, there is no metadata in the LIVE environment. At the moment the only possibility for the user is, that he overwrites the meta data, because this meta data connected with the explicit content element can be published by the user through the workflow.
A solution of the problem would be to publish meta data of a file which is immediately live also immediately live (without any action of the user). Another solution would be to make the meta data in the workflow management accessible for the user (the problem may be, that the meta data of files is handled on the root page, which is not accessible for users especially in a multi-domain-site).
The preferred solution would be to integrate the fileadmin fully in the workflow management and to have an approval process which links the file and the meta data together and a possibility for the user to publish these to the LIVE environment.
Updated by Alex Kellner about 10 years ago
The description of this ticket is a bit different to my problem. But I have the same symptom. I described it in #60343
Maybe this is related to my problem
If a user integrates the uploaded file in a content element in the workflow and sees the metadata there (grey letters) and does not overwrite it, there is no metadata in the LIVE environment. At the moment the only possibility for the user is, that he overwrites the meta data, because this meta data connected with the explicit content element can be published by the user through the workflow.
Updated by Helmut Hummel about 10 years ago
- Status changed from New to Closed
This is indeed a duplicate of #60343