Uploaded image for project: 'In-Portal CMS'
  1. In-Portal CMS
  2. INP-402

Create more control over sent emails

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 5.0.2-B1
    • Fix Version/s: 5.2.0-B3
    • Component/s: Front End
    • Labels:
      None
    • Additional information:
      Hide

      Add "use_custom_design" parameter during e-mail sending to allow excluding e-mail design usage for individual e-mail events.

      Show
      Add "use_custom_design" parameter during e-mail sending to allow excluding e-mail design usage for individual e-mail events.
    • Change Log Message:
      Allows to centrally specify all e-mail design template
    • Story Points:
      1
    • External issue ID:
      485
    • Copy Issue Key:
    • Patch Instructions:

      Patches must be submitted through Phabricator.

      Description

      We have engine, that allows to sent emails based on user actions throughout the system. Each email content can be directly specified for each language. In case if there is need to create common footer for all sent emails, that site administrator could edit "COMMON.FOOTER" event content and place requested text there.

      Such approach doesn't allow to style all sent emails (e.g. styles, images, etc.). I propose to create 2 fields in language record: HtmlEmailTemplate and TextEmailTemplate. Possible format of this variable could be:

      <html>
      	<head>
      		<title>$subject</title>
      	</head>
      	<body>
      		$body
      	</head>
      </html>
      

      Of course <inp2: style tags also could be allowed inside this template. Because of emails are sent from administrative console and from Front-End all paths to external resources like images, styles must be absolute. Contents of current COMMON.FOOTER event should be moved to HtmlEmailTemplate field in format "$body footer here".

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                alex Alex
                Reporter:
                alex Alex
                Developer:
                Alex
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: