Project

General

Profile

Actions

Bug #34144

closed

Cannot go back to overview of changes

Added by Xavier Perseguers over 12 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Workspaces
Target version:
-
Start date:
2012-02-21
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

When opening workspaces Backend module without selecting a page in the page tree, an overview of pending changes is shown. However, once a page has been selected, there is no way to go back to this overview of pending changes.


Files

Actions #1

Updated by Gerrit Code Review over 12 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/9135

Actions #2

Updated by Gerrit Code Review over 12 years ago

Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/9135

Actions #3

Updated by Tolleiv Nietsch over 12 years ago

Maybe we should "just" use the icon which already exists in the list module?

Actions #4

Updated by Wouter Wolters over 11 years ago

  • Status changed from Under Review to New

Patch was rejected in Gerrit because lack of interest.

Actions #5

Updated by Michael Stucki almost 11 years ago

  • Category set to Workspaces
Actions #6

Updated by Michael Stucki almost 11 years ago

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

Updated by Mathias Schreiber almost 10 years ago

  • Target version set to 7.5
Actions #8

Updated by Benni Mack about 9 years ago

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

Updated by Mathias Schreiber about 9 years ago

  • Target version deleted (7 LTS)
  • Is Regression set to No
Actions #10

Updated by Riccardo De Contardi almost 7 years ago

  • Status changed from New to Closed
  • Assignee deleted (Xavier Perseguers)

As far as I can read from the comments on the attached patch, this should have been solved since 4.7, therefore I think I can safely close it .

If you think that this is the wrong decision or experience the issue again, please reopen it or open a new issue with a reference to this one. Thank you.

Actions

Also available in: Atom PDF