Project

General

Profile

Actions

Bug #81633

closed

StagesService->getBackendUsers should provide 'lang' and 'uc' attribute

Added by Kevin Ditscheid about 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Workspaces
Target version:
-
Start date:
2017-06-20
Due date:
% Done:

0%

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

Description

The method for getting the BackendUsers via the \TYPO3\CMS\Workspaces\Service\StagesService does not provide the 'lang' of a BackendUser.
This is problematic when reaching the notifyStageChange method of the \TYPO3\CMS\Version\Hook\DataHandlerHook, because the recipients could be given to this method via the $notificationAlternativeRecipients parameter and thus won't be processed by getEmailsForStageChangeNotification but simply be copied to $emails which later defines the language of the E-Mail template for the recipients. The result will be E-Mails that does not have the same language as the BackendUser selected for his account.
This is only affecting workspaces mainly through the \TYPO3\CMS\Workspaces\ExtDirect\ActionHandler class and the backtraces are extremly complicated.

The method \TYPO3\CMS\Workspaces\ExtDirect\ActionHandler->getRecipientList also needs the 'uc' attribute of the BackendUser, which is not provided as far as I can see.

All this would be fixed by simply adding `lang, uc` to the field select list of the getBackendUsers method of \TYPO3\CMS\Workspaces\Service\StagesService


Related issues 1 (0 open1 closed)

Is duplicate of TYPO3 Core - Bug #46217: Notification emails not translated for default recipientsClosed2013-03-12

Actions
Actions #1

Updated by Kevin Ditscheid about 7 years ago

  • Is duplicate of Bug #46217: Notification emails not translated for default recipients added
Actions #2

Updated by Kevin Ditscheid about 7 years ago

Whups, done a duplicate here, could someone close this?

Actions #3

Updated by Mona Muzaffar about 7 years ago

  • Status changed from New to Closed

closed - as request by Kevin

Actions

Also available in: Atom PDF