Project

General

Profile

Actions

Bug #16370

closed

stage change notification mail shows SQL table name instead of TCA title

Added by Martin Kutschker over 18 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Should have
Category:
Workspaces
Target version:
-
Start date:
2006-07-19
Due date:
% Done:

0%

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

Description

The mail displays the changed item as tablename:uid. This internal data may be given as additional information, but what should be sent is the TCA title of the table and the TCA title of the record.

(issue imported from #M3877)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Feature #16913: Notification email with more details and optionsClosed2007-01-28

Actions
Actions #1

Updated by Michael Stucki almost 11 years ago

  • Category changed from Miscellaneous to Workspaces
Actions #2

Updated by Michael Stucki almost 11 years ago

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

Updated by Mathias Schreiber almost 10 years ago

  • Target version set to 7.5
Actions #4

Updated by Benni Mack about 9 years ago

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

Updated by Benni Mack about 9 years ago

  • Description updated (diff)
  • Status changed from Accepted to Needs Feedback
  • Target version deleted (7 LTS)
  • Is Regression set to No

we reworked the notification email system for 7.5 - could you please check if the problem still exists?

Actions #6

Updated by Marc Wöhlken about 9 years ago

Behavior has not changed. Example for generated mail text:

---
Subject:
TYPO3 Workspace Note: Stage Change for tt_content:171, sys_file_reference:103

Body:
At the TYPO3 site "My test site" (http://mytestsite.tld/typo3/)
in workspace "Example workspace" (1)
the stage has changed for the element(s) "Changed a heading" (tt_content:171, sys_file_reference:103) at location "/Congratulations/Features/" in the page tree:

=> Ready to publish

User Comment:
"My first content update"

State was changed by (username: v7test)
---

IMHO it would be much better to change it like this:

---
Subject:
TYPO3 Workspace Note: Stage Change for content element 171, file reference 103

Body:
At the TYPO3 site "My test site" (http://mytestsite.tld/typo3/)
in workspace "Example workspace" (1)
the stage has changed for the element(s) "Changed a heading" (content element tt_content:171, file reference sys_file_reference:103) at location "/Congratulations/Features/" in the page tree:

=> Ready to publish

User Comment:
"My first content update"

State was changed by (username: v7test)
---

The intended audience for this mail are editors which may not have the technical background to relate table names to the elemnts changed in BE. So I would really prefer "translated" (tt_content --> content element) descriptions of what's going on. The neccessary information can probably be fetche from TCA.

Maybe it would be even more helpful to change the subject of the workspace notification to something simpler like:
"TYPO3 Workspace Note: Stage Change fpr page /Congratulations/Features/".

This would relate changes to something really simple (a page) which is a concept all editors should understand. It would also help to understand the relevance of a change much easier as editors could easily understand which page (branch) has changed.

Actions #7

Updated by Oliver Hader almost 9 years ago

  • Status changed from Needs Feedback to Closed

The subject can be modified using Page TSconfig, see https://docs.typo3.org/typo3cms/extensions/workspaces/latest/singlehtml/Index.html#configuration-options

tx_version.workspaces.stageNotificationEmail.subject = TYPO3 Workspace Note: Stage Change for "###RECORD_TITLE###" (###ELEMENT_NAME###)

In general, the notification template handling is a... it's sub-optimal. Thus, rewriting it and enable HTML message would make more sense.
The current marker-based logic comes to an end with many records that might be nested or dependent as well.

Actions

Also available in: Atom PDF