Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • We can change the generic footer by overriding footer.html under the project folder. If, only the text part has to be changed, we can edit the value of email_template_footer_part_one key of bov3/wcm bundle.

  • We can also change the specific footers by overriding them under the project folder.

  • We can also add new specific files as headers, footers, or styles. In this case, the email HTML file needs to be updated to use the newly added specific header, footer, or style.

  • All bodies content can be changed by overriding them under the project folder and by using placing them under the correct path in email html file. Therefore the email html files like WXM_CART2/res/email/collaborate.html should also be overriden under __perso/email/project/ file tree structure.

    • Example with cart share email :

      • I’ll create a file named share.html which will contain the main body of my email. I’ll then place it under __perso/email/project/bodies/ . Then when a board is shared, my body content will be used inside the template with the header and the footer.

Note

The file structure has to be respected for the template system to work properly. If I had created a share.html file directly under __perso/email/project/ I would have overitten the template (and not the body) of the email generated on a board share. In this case i will not have the header and the footer in my email

  • All bodies content can be changed by overriding them under the customization folder defined in the plugins (WXM_CART2 and PACKAGED_RegistrationEmails)

    • Example with cart share email :

      • I’ll create a file named share.html which will contain the main body of my email. I’ll then place it under __perso/emailTest/ in a new folder called bodies. This path has also been set in the params of WXM_CART2. Then when a board is shared, my body content will be used inside the template with the header and the footer.

Note

The file structure has to be respected for the template system to work properly. If I had created a share.html file directly under __perso/emailTest/ I would have overitten the template (and not the body) of the email generated on a board share. In this case i will not have the header and the footer in my email

3/ Backward compatibility

...