Bug #54795
closed
EXT:version - Unable to switch versioned tt_content records
0%
Description
Full story (no answers)
http://forum.typo3.org/index.php/t/201013/
Short
Prerequisites:
CMS: TYPO3 6.1.7 (vanilla install - not updated from previous versions)
Ext:version installed (default?!)
Ext:workspaces not installed
Problem:
1: Record "#" (tt_content:#) cannot be swapped or published independently, because it is related to other new or modified records.
Reason:
\TYPO3\CMS\Version\DataHandler\CommandMap::applyWorkspacesDependencies()
L:458 $dependentElements = $dependency->getNestedElements($outerMostParent);
$dependentElements returns two entries:
"tt_content:#" (expected result) and ":" (unexpected second key with missing table and uid)
The second key will produce the above Error (reproducible on another 6.1.7 machine) making it impossible to switch any records.
- WEB > List/Page > new tt_content Element
- WEB > List > version > new version
- WEB > List > version > swap = above error
Background:
We are preparing our extensions from 4.5 to 6.2 for a new project but since it was delayed we start migrating to 6.1 which was suggested by the TYPO3 Team.
Updated by Oliver Hader over 10 years ago
- Status changed from New to Needs Feedback
This means, you are not using a workspace at all - but you're using the version functionality?
Please give it another try with TYPO3 6.2 RC1 - I guess it might be related to problems with sys_file_reference (thus, on text w/image elements)...
Updated by Vitoandre D'Oria over 10 years ago
Yes in this case we are only using the version extension. WS was imho too to often changed/redone in the last years and might be a overkill for smaller projects/companies (i hope this changes someday).
@Markus Raab told me the problem exists at least since 6.0 (FAL was introduced in that TYPO3 version). So that would speak for your theory.
We just tested "Text" and "Text & Image" on 6.2.0rc1:
Text: OK
Text & Image:
1: Record "version Test v1" (tt_content:169) cannot be swapped or published independently, because it is related to other new or modified records.
Indeed its seems to be FAL related.
Updated by Alexander Opitz about 10 years ago
Hi,
does the problem still exists within newer versions of TYPO3 CMS (6.2.4)?
Updated by Alexander Opitz almost 10 years ago
- Status changed from Needs Feedback to Closed
- Target version deleted (
next-patchlevel)
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.