Project

General

Profile

Actions

Bug #22184

closed

Moving inside workspace selects wrong move-destination

Added by Stefan Neufeind over 14 years ago. Updated about 14 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2010-02-25
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.3
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Setup for testcase:
Have three tt_content-records in list-view. Two of them have move-placeholders (see attached screenshot).

How to reproduce:
1) Setup testcase.
2) Go to the workspace, so you actually see three tt_content-elements.
3) Try to move the lowest item up one step.

Expected:
Should select sorting-ID of the workspace-version (move-placeholder!) of the second row and try to move it before that element (seen from sorting-enumeration).

Actual result:
As move-destination (to find the new sorting-value needed for item 3) the live-version or item 2 is taken.

(issue imported from #M13658)


Files

move_placeholder.jpg (32.3 KB) move_placeholder.jpg Administrator Admin, 2010-02-25 13:48

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #23741: Live workspace does not respect move-to-placeholdersClosedBenni Mack2010-10-15

Actions
Actions #1

Updated by Benni Mack about 14 years ago

Hey Stefan,

I'd say that this issue is related to #16005, where I've sent a patch to the TYPO3 core list. With the patch applied the MOVE_TO_PLACEHOLDER records are not shown (and not taken into account when sorting). Thus, I'd say that this is the expected behaviour (not worrying about the placeholders).

Please let me know if this solves your problem and I could resolve the issue.

Actions #2

Updated by Stefan Neufeind about 14 years ago

Tried to replicate the problems I found at that time (already quite a while ago) now with TYPO3 4.4.4. Besides the placeholders showing up in the live-version (which I agree is somewhat "wrong") it already seems to take things into account correctly for moving up/down (sorting).
So I assume there has been some change from 4.3.x to 4.4.x now that at least the sorting-behaviour already got fixed in some way. I'd suggest to close this here as "meanwhile fixed".
I also agree that your patch for 16005 sounds good to have in as well (not showing the placeholders).

Actions #3

Updated by Benni Mack about 14 years ago

Hey Stefan.

Yes. then it's fixed in all the next versions (16005 was committed to trunk).

Thanks
Benni.

Actions

Also available in: Atom PDF