DEPRECATION WARNING
This documentation is not using the current rendering mechanism and is probably outdated. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.
EXT: My Extension¶
| Author: | Kasper Skårhøj |
|---|---|
| Created: | 2002-11-01T00:32:00 |
| Changed: | 2009-07-24T12:42:50 |
| Author: | Author Name |
| Email: | your@email.com |
| Info 3: | |
| Info 4: |
EXT: saveDocEmail¶
Extension Key: marit_saveDocEmail
Copyright 2000-2009, Marit AG, Marco Huber, < typo3-extension@marit.ag >, www.marit.ag
This document is published under the Open Content License
available from http://www.opencontent.org/opl.shtml
The content of this document is related to TYPO3
- a GNU/GPL CMS/Framework available from www.typo3.com
Table of Contents¶
EXT: saveDocEmail 1
Introduction 2
What does it do? 2
Screenshots 2
Installation 2
Configuration 2
UserTSconfig 2
Known problems 3
To-Do list 3
Changelog 3
Introduction¶
What does it do?¶
XCLASSing alt_doc.php and hooking class.t3lib_tcemain.php to get a Button "Save doc and send email to FE-Groups which have access to this Element" in the Backend. Similar to the button "Save and new".
Email text, sender and subject are configurable by userTSconfig.
Screenshots¶
Abbildung 1: New Button
Abbildung 2: send Mail to this groups' users
Abbildung 3: Edit the email's text and subject
Installation¶
Install the extension with the Extension Manager. Configure it with userTSconfig.
Configuration¶
UserTSconfig¶
options.saveDocEmail¶
a
options.saveDocEmail
options.saveDocEmail.[table]
b
0 or 1
c
Activate the button
options.saveDocEmail.sender_email¶
a
options.saveDocEmail.sender_email
options.saveDocEmail.[table].sender_email
c
Sender's email address
options.saveDocEmail.sender_name¶
a
options.saveDocEmail.sender_name
options.saveDocEmail.[table].sender_name
b
String
c
Sender's name
options.saveDocEmail.subject¶
a
options.saveDocEmail.subject
options.saveDocEmail.[table].subject
b
String
c
This string can have some placeholders:
- %1$s = Recipient's firstname
- %2$s = Recipient's lastname
- %3$s = Recipient's title
- %4$s = Recipient's email address
- %5$s = Recipient's company
Example:
“options.saveDocEmail.subject = %1$s %2$s, %5$s: There are new News!”
options.saveDocEmail.text¶
a
options.saveDocEmail.text
options.saveDocEmail.[table].text
b
String
c
This string can have some placeholders:
- %1$s = Recipient's firstname
- %2$s = Recipient's lastname
- %3$s = Recipient's title
- %4$s = Recipient's email address
- %5$s = Recipient's company
Example:
“options.saveDocEmail.tx_dam.text (
Dear %3$s %1$s %2$s,
There are new dokuments which you can download.
Kind regards,
Your team
)”
options.saveDocEmail.utf8¶
a
options.saveDocEmail.utf8
options.saveDocEmail.[table].utf8
b
2 or 1 or 0
c
- 2 sends database values through utf8_encode()
- 1 sends database values through utf8_decode()
- 0 sends the database values through nothing
options.saveDocEmail.modifySubjectAndText¶
a
options.saveDocEmail.modifySubjectAndText
options.saveDocEmail.[table].modifySubjectAndText
b
0 or 1
c
If set to 0 then the BE-User is not able to edit the email's subject and text
If [table] is set, the option is only for this table. So if you say options.saveDocEmail.tt_new = 1 and options.saveDocEmail = 0 then you have the button only when you edit news.
Known problems¶
To-Do list¶
Changelog¶
EXT: marit_csvimport - 4