Project

General

Profile

Actions
Copy link

Bug #50960

closed

Mass actions not working

Added by Marius S. over 11 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Workspaces
Target version:
7 LTS
Start date:
2013-08-09
Due date:
% Done:

0%

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

Description

All mass actions return "Done processing 0 elements" no matter how much changed elements the workspace has or which workspace you selected.

Files

mass-action-processed.png (32.3 KB) mass-action-processed.png Marius S., 2013-08-09 12:33
Actions
Copy link
 #1

Updated by Marius S. about 11 years ago

Don't know if this is the best way but:

/typo3/sysext/workspaces/Classes/Service/WorkspaceService.php
Line 131 & Line 157

if I change the -1 to 0 in the function selectVersionsInWorkspace the publish and discard mass action works great.

Actions
Copy link
 #2

Updated by Michael Stucki almost 11 years ago

  • Category set to Workspaces
Actions
Copy link
 #3

Updated by Michael Stucki almost 11 years ago

  • Project changed from 624 to TYPO3 Core
  • Category changed from Workspaces to Workspaces
Actions
Copy link
 #4

Updated by Mathias Schreiber almost 10 years ago

  • Target version set to 7.5
Actions
Copy link
 #5

Updated by Oliver Hader about 9 years ago

  • Status changed from New to Needs Feedback
  • Target version changed from 7.5 to 7 LTS
  • Is Regression set to No

Is this still existing in recent TYPO3 versions?

Actions
Copy link
 #6

Updated by Riccardo De Contardi almost 9 years ago

  • Status changed from Needs Feedback to Closed

I've done a test with both 6.2.16 and the latest master (8.0-dev) and in both cases the number of the processed elements is shown, so I think I can close this issue (I have tested with both the "discard" and "publish" mass action); moreover, there has been no feedback within the last 90 days.

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.

Actions
Copy link

Also available in: Atom PDF