Bug #44737
closedCustom stage changes do NOT send email notifications
0%
Description
With Typo3 4.6.15 email are not send when the stage is send to a stage "review" I've add in custom workspace.In some worskspace email is send for this stage ...
When the content is send to stage "ready to publish" an email is send ...
Updated by Oliver Hader almost 12 years ago
- Priority changed from -- undefined -- to Should have
Updated by Oliver Hader almost 12 years ago
- Status changed from New to Needs Feedback
- Assignee deleted (
Marco Bresch) - Target version changed from 4.6 to 4.5.23
Did you configure recipients on your custom "review" stage?
And if so, is the dialog window with the possible recipients shown when forwarding elements to the "review" stage?
Updated by Myriam Bernard almost 12 years ago
Yes recipients are configured for the custom stage
and pop up dialog box is shown
edit :
I've just change this in "Recipient suggestion checkboxes" :
before the choice was :All are selected per default (can be changed)
now I've choose : All are selected per default (cannot be changed)
And it's seems to send email notification ...
Updated by Robert Vock over 11 years ago
I've got the same Problem (TYPO3 4.7.12)
The problem is, that if you choose "All are selected per default (cannot be changed)", you get a list of checkboxes, which are checked, but disabled.
Browsers (at least Chrome) do not send the value of disabled form fields. So if you submit the form, the values of the checkboxes are not sent.
The function Tx_Workspaces_ExtDirect_ActionHandler::getRecipientList should get a list of backend users which should be notified. It tries to do that on line 248:
245: if (intval($notification_mode) === Tx_Workspaces_Service_Stages::MODE_NOTIFY_ALL || intval($notification_mode) === Tx_Workspaces_Service_Stages::MODE_NOTIFY_ALL_STRICT) { 246: // get the default recipients from the stage configuration 247: // the default recipients needs to be added in some cases of the notification_mode 248: $default_recipients = $this->getStageService()->getResponsibleBeUser($stageId, true);
If I change the true to false, it works for me. I do not know if there are other consequences or if this is the correct fix for this bug.
Updated by Michael Stucki almost 11 years ago
- Category changed from Bugs to Workspaces
Updated by Michael Stucki almost 11 years ago
- Project changed from 624 to TYPO3 Core
- Category changed from Workspaces to Workspaces
Updated by Alexander Opitz over 10 years ago
- Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.1.7)?
Updated by Alexander Opitz over 10 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this ticket.
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.