Bug #60343
closed
Added by Gerhard Rupp over 10 years ago.
Updated about 6 years ago.
Estimated time:
(Total: 0.00 h)
Description
Metadata retrieved from table sys_file_metadata does not recognize workspaces. Therefore users in a draft workspace canĀ“t make use of metadata. (Metadata of new files in the LIVE-workspace is empty by default of course.)
Hi,
I think I have the same issue here.
I try to describe it a bit more.
If you're using workspaces and have editors, you have to select DB-Mount-Points for the be_groups. You can let the DB-Mount-Points empty for workspaces but normally you would also select a page. Letting Mount-Points empty for groups had the effect, that the editor have no pages in pagetree. Selecting root is possible for both records as long as you click on save - after a reload "0" is removed.
This is the main issue. Because records of type sys_file_metadata have pid=0 per default. So the editor has no chance to publish a sys_file_metadata record in TYPO3
Configuration
- TYPO3 6.2.6
- Draft Workspace
- BE-User (editor) with most available rights (really all tables)
How to reproduce
- Editor change workspace to draft
- Upload an image in filelist to any folder
- Edit the record and save some title, altText, description
- Editor will also create a new content record (type Image) with a relation to the uploaded image before
- The default title of the image should be used (also description and altText)
- The editor (or another editor) is going to publish the changes, but in Workspace Module only the new tt_content element is shown (not the metadata-record)
Workarround
- A quick proof confirmed: Changing the pid of the metadata-record directly in the database to any existing page (where the publishing-editor has access to) will help. Now it's possible to publish both records
- So, if I would create an extension with a small TCA configuration to extend sys_file_metadata, I could insert a value to field PID.
BTW: I'm not totally sure but I think ticket #62537 could be related to this one
- Status changed from New 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/34156
Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/34183
Patch set 2 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/34183
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved 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/34188
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/34188
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/34188
Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/34188
- Parent task set to #58284
- Assignee set to Helmut Hummel
Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/34270
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF