Project

General

Profile

Actions

Bug #52689

closed

List module shows table header even there is no record anymore on that page

Added by Sascha Egerer over 10 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Workspaces
Target version:
Start date:
2013-10-11
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
hard
Is Regression:
No
Sprint Focus:

Description

If you move a record form page A to page B on page A the table for the record is still displayed even if there is not record anymore.

Testplan:
  • Create page A and B in live workspace
  • Add a tt_content record to page a in live workspace
  • switch to a workspace
  • move the tt_content record from page A to page B

Expected Result:
The list Module should shows no content and also no tables on page A

Current Result:
The list module show the tt_content table header with "tt_content (1)" but shouldn't because there is no record anymore on that page (technically it is but this should be checked here).


Files

ws.png (19.8 KB) ws.png Sascha Egerer, 2013-10-11 10:50
Actions #1

Updated by Michael Stucki over 10 years ago

  • Category set to Workspaces
Actions #2

Updated by Michael Stucki over 10 years ago

  • Project changed from 624 to TYPO3 Core
  • Category changed from Workspaces to Workspaces
Actions #3

Updated by Mathias Schreiber over 9 years ago

  • Target version set to 7.4 (Backend)
  • Complexity set to hard
  • Is Regression set to No
Actions #4

Updated by Mathias Schreiber about 9 years ago

  • Target version changed from 7.4 (Backend) to 7.5
Actions #5

Updated by Oliver Hader over 8 years ago

  • Status changed from New to Needs Feedback
  • Target version changed from 7.5 to 7 LTS

Should be solved with one of the placeholder patches for 7.5, right?

Actions #6

Updated by Riccardo De Contardi over 8 years ago

  • Status changed from Needs Feedback to Closed

I've performed the test reported in the description on both 6.2.17 and 8.0-dev (latest master) and I can't reproduce the problem, so I close this issue.

If you think that this is the wrong decision or experience this issue again or there are more test that should be done, 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.

Thank you

Actions

Also available in: Atom PDF