[TYPO3-dev] Email Notification - Cron or Hooks?

[Patrick Gaumond]

Gerrit Kamp wrote:

> My idea is to make an Admin FE UI in which certain events and responses are
> defined. This UI contains for each notification type:
> -        Text input, SQL: definition of an event
> -        Text input, HTML: message with ###markers### for the SELECT fields
> -        Text input, SQL: conditions for which users should get the message
> (the main condition is of course that the FE user has indicated he/she WANTS
> to be notified)
> -        button to test (no emails will be sent, but a result screen shows
> which events are selected by the SQL, what the message will look like, and
> to which users it would have been sent)
> -        button to switch the notification on or off
>  
> Is rather straightforward.

Without some kind of SQL wizard (like in the BE under DB Check-> Search 
Whole DB -> Advanced Query) it will be hard to setup for "normal" (read 
non-geek).

 > For my current project, I select for example
> that only Owners and Co-owners of certain records should be notified on
> record changes, which is already a very customized SQL select query.

New record would be important to be notified, no?

>> You'll have to deal with errors in emails too.  ;)
> What do you mean? Emails to wrong addresses that get bounced?

Yep, bouncing. And people that get fired.  ;)


>> Bacn is:
>> "Notifications you want. But not right now"
>  
> This seems to be something that FE users should worry about, don't see how I
> can incorporate it into the extension, right?

I was just reading about it while I was answering your post and found 
the synchronicity funny enough to mention it.

People that will use your system *will* get bacn! (and asked for it) ;)

Your system is in fact a bacn generator...

Patrick