Project

General

Profile

Actions

Bug #17549

closed

Usability: after editing WS versions, go back to the previously showed list view

Added by Oliver Klee over 16 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Workspaces
Target version:
-
Start date:
2007-08-22
Due date:
% Done:

0%

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

Description

Steps to reproduce:

1. Switch to the draft workspace.

2. In the list view, click on a table name to only show records from that table.

3. Edit a record to create a new version.

4. Click on the yellow "1" to go to the list of versions of that record.

5. Click on the "back to list view" icon (the second icon from the left).

Expected results:

The list view of only the previously selected table is shown (and, even better, even the selected page of the list view, see issue #0006191).

Actual results:

The list view of all tables on that page is shown.

(issue imported from #M6192)


Files

6192.diff (1.13 KB) 6192.diff Administrator Admin, 2009-01-22 22:39

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #79942: Move version selector view to EXT:compatibility7ClosedBenni Mack2017-02-21

Actions
Actions #1

Updated by Christian Kuhn about 15 years ago

Confirmed.

This is still valid in current trunk (rev 4608).

Actions #2

Updated by Christian Kuhn about 15 years ago

Taking a deeper look I was unable to find a simple way on how to solve this in a consistent way:

The button says "Show record list". It does not say "Return to previous chosen list view". So the button reacts exactly the same as a click on the list item in the main module menu. One could say this issue is not a bug at all ;-)

- My preferred solution is to remove the "Show record list" icon. It's probably impossible to make it always react like the user expected, especially if the versioning module was called from different sources (from clickmenu in page tree, from main module list, from list modul, ...). I guess most people don't use the icon anyway. We could then still fix / use the returnUrl handling in the versioning module and add a "Go back" button to the docheader like its done for the "History / undo" module.

- A way to fix the icon link could be to add an additional GET parameter "singleview=1" if the module is called from list module single view, keep this param through all follow up links in the versioning module, and set the table=xy param for the icon link if that parameter was present. Awful hack, I won't do that.

- Another way would be to add the returnUrl parameter to the link in the list view (like it's also done for the history / undo show_rechis module), fix / review the current messing with the returnUrl handling in the versioning module, and correct the "Show record list" icon link to take the returnUrl parameter into account if it included "db_list.php" and "table=xy" or something. That is also awful and wouldn't help too much from a usability point of view.

I could compile a (trivial) patch to completely remove the icon from the docheader, but I will currently not dig any deeper into the returnUrl handling of the versioning module. That is just too much trouble for this tiny icon ...

Actions #3

Updated by Christian Kuhn about 15 years ago

Added a patch to remove the icon from the module :)

Actions #4

Updated by Michael Stucki over 10 years ago

  • Category changed from Miscellaneous to Workspaces
Actions #5

Updated by Michael Stucki over 10 years ago

  • Project changed from 624 to TYPO3 Core
  • Category changed from Workspaces to Workspaces
  • Target version deleted (0)
Actions #6

Updated by Mathias Schreiber about 9 years ago

  • Target version set to 7.5
Actions #7

Updated by Benni Mack over 8 years ago

  • Target version changed from 7.5 to 7 LTS
Actions #8

Updated by Mathias Schreiber over 8 years ago

  • Target version deleted (7 LTS)
Actions #9

Updated by Christian Kuhn over 3 years ago

  • Related to Task #79942: Move version selector view to EXT:compatibility7 added
Actions #10

Updated by Christian Kuhn over 3 years ago

  • Description updated (diff)
  • Status changed from Accepted to Closed

This issue has been solved with #79942 in v8 where the version (not workspace) module has been moved to compat7 extension and later been removed.

Happily closing this old issue now ;)

Actions

Also available in: Atom PDF