Bug #66507
closedFAL metadata empty in reference from read only storage
Added by Heinz Schilling over 9 years ago. Updated over 5 years ago.
100%
Description
When a image from a read only storage is referenced the metadata is empty. Override ""? Same image from read write storage shown the default metadata.
Image: top is from read/write storage. Bottom from same file referenced via read only storage.
Files
Bildschirmfoto 2015-04-21 um 07.33.19.png (60.9 KB) Bildschirmfoto 2015-04-21 um 07.33.19.png | Heinz Schilling, 2015-04-21 07:34 |
Updated by Frans Saris over 9 years ago
- Status changed from New to Needs Feedback
You also filled the metadata (caption and alt text) for the image in the read-only storage?
gr. Frans
Updated by Heinz Schilling over 9 years ago
I made a structure like this:
/storage/shared/file.jpg
Two "file storages" to the same folder:
/storage/
One file storage (/storage read/write) is writable and the other one (/storage read only) it's not. I upload the image via (/storage read/write) and set meta data. The reference the image via (/storage read only) and get the image but can't see the meta data.
The file and the meta data exists only once.
Greetings, Heinz
Updated by Frans Saris over 9 years ago
Are you really using storages for this?
A folder should only be addressed by 1 storage. If you want to restrict parts of a storage for certain editors used File mounts.
If you assign a folder (or part of a folder structure) to multiple storages this will give you unwanted side-effects.
gr. Frans
Updated by Heinz Schilling over 9 years ago
Yes I used storages for this. The access rights are easy to configure.
I tried it with file mounts but can't protect metadata. User rights sum and table 'sys_file_metadata' can be written (needed in other file mount).
Is it not possible to mount a folder as storage twice?
Updated by Frans Saris over 9 years ago
Using 2 storages for 1 folder give problems with indexing new files but also with keeping track/cleanup of deleted files. You should make sure that no storage root folder is the same or a subfolder of an other storage.
For 6.2 the configuration of readonly file mounts is indeed a little bit harder then configuring a readonly storage, this has changed in TYPO3 7.
What exactly goes wrong when you try the readonly file mount approach? Maybe we can fix something there so that it works.
Gr. Frans
Updated by Heinz Schilling over 9 years ago
it's possible to access metadata from read only filament. Usergroup has a read only filemount and a normal filemount. For the normal filemount I need access rights on table file metadata.
Way to access: Put a image from read only filemount in content. Use [i] for information about the file. In the popup you can find "References to this items" and editing of metadata in read only filament is possible.
Updated by Frans Saris over 9 years ago
Currently the metadata access is not bind to the filemount permissions
Updated by Gerrit Code Review over 9 years ago
- Status changed from Needs Feedback to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/42874
Updated by Gerrit Code Review about 9 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/42874
Updated by Gerrit Code Review almost 8 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/42874
Updated by Nicole Cordes over 6 years ago
- Status changed from Under Review to Accepted
Updated by Gerrit Code Review about 6 years ago
- Status changed from Accepted to Under Review
Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/42874
Updated by Gerrit Code Review about 6 years ago
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58335
Updated by Anja Leichsenring about 6 years ago
- Has duplicate Task #86317: [BUGFIX] Make meta data editable for non-writable storages added
Updated by Gerrit Code Review about 6 years ago
Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/42874
Updated by Gerrit Code Review about 6 years ago
Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/42874
Updated by Gerrit Code Review about 6 years ago
Patch set 7 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/42874
Updated by Gerrit Code Review about 6 years ago
Patch set 8 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/42874
Updated by Gerrit Code Review almost 6 years ago
Patch set 1 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58978
Updated by Nicole Cordes almost 6 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset c3fef10f153e19179e6dea90307a25e1f135ba3b.
Updated by Gerrit Code Review almost 6 years ago
- Status changed from Resolved to Under Review
Patch set 2 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58978
Updated by Nicole Cordes almost 6 years ago
- Status changed from Under Review to Resolved
Applied in changeset f9c6e31d91ad32ea71b8bc30d5a6b19556287376.