Skip to main content

Custom email templates in Magento2

Custom email templates in Magento2



In this blog, we’ll discuss how we can create custom email templates and insert variables in email templates of magento2. 


Declare email template 


Create email_templates.xml inside Vendor/Module/etc/ folder. 


<?xml version="1.0" encoding="UTF-8"?>

<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

      xsi:noNamespaceSchemaLocation="../../../Magento/Email/etc/email_templates.xsd">

  <template id="custom_module_email_template" label="custom_module_email_template" file="custom_email.html" type="html" module="Blog_Management" area="frontend" />

</config>


Here, 

Id is a unique identifier for email templates which we’ll use while declaring which email template we want to use while sending email. 

label is a displayed name of an email template. 

file is a html file in which is used to render html content for email templates. 

module is used to define the vendor_module name in which we are creating this email template. 

area is used to find email template files in adminhtml or frontend. 


Create email template file


Now, create custom_email.html file inside Vendor/Module/view/frontend/email/ folder. 


<!--@Subject Email Template @-->

<!--@vars

{"store url=\"\"":"Store Url",

"skin url=\"images/logo_email.gif\" _area='frontend'":"Email Logo Image"}

@-->

<!--@styles

body,td { color:#2f2f2f; font:11px/1.35em Verdana, Arial, Helvetica, sans-serif; }

@-->

{{template config_path="design/email/header_template"}}

<p>{{trans "Hi "}} {{var customer_name}},</p>

<p>

{{trans "Thank You for Registering,"}}

{{trans "We will send You Link along with the Password for you to log in. Stay connected for updates."}}

</p>

{{var message}}

{{template config_path="design/email/footer_template"}}

 


trans is used before the text you want to translate while using a multilingual store. 


We have to pass the variable values while sending email like this:- 


$storeId = $this->storeManager->getStore()->getId();

       $from = ['email' => $fromEmail, 'name' => $fromName];

       $this->inlineTranslation->suspend();

       $storeScope = \Magento\Store\Model\ScopeInterface::SCOPE_STORE;

       $templateOptions = [

           'area' => \Magento\Framework\App\Area::AREA_FRONTEND,

           'store' => $storeId

       ];

       $templateId = 'custom_module_email_template'; // template id

       $templateVars = array( //Create array to pass the variables

           'store' => $this->storeManager->getStore(),

           'customer_name' => 'Sakshi Bissa',

           'message'   => 'Thankyou.'

         );

       $transport = $this->transportBuilder->setTemplateIdentifier($templateId, $storeScope)

           ->setTemplateOptions($templateOptions)

           ->setTemplateVars($templateVars) // pass variables

           ->setFrom($from)

           ->addTo($toEmail)

           ->getTransport();

       $transport->sendMessage();

     $this->inlineTranslation->resume();

 


We can access these variables inside the html file using {{var customer_name}}. That's all. 




Labels:

Comments

Post a Comment

Popular posts from this blog

Magento2 CLI

Magento2 CLI  Back after a long break! Starting again with this blog because I found it the most important to understand if we are doing the magento development as magento commands play the most important role here. It really helps us a lot if we know that lĺwhich command we need to run on this action or after any changes.  Let’s start with the basic commands that we use a lot of times during our development.  cache:clean or cache:flush php bin/magento cache:clean Or  php bin/magento  cache:flush Both of these commands are used to clean the cache of Magento2 so that your new changes can be reflected to your store.  Using cache:clean it deletes all the enabled cache of magento2. Disabled caches are not affected with cache:clean but if you are doing cache:flush then it purges all the cache storage of magento wherever its enabled or disabled or it even deletes all the third party cache along with the magento cache.  If you are doing any changes in admin configuration, layout xml file, u
Post a Comment
Read more

How EAV Model Works in Magento2?

                         How EAV Model Works in Magento2?  EAV Model stands for Entity-Attribute-Value is a very important concept of magento2 to understand how the attributes of entities are stored and works in magento2.  EAV Model is described as :-  Entity - Entity refers to the data items such as customers,orders,catalog,category etc.  Attribute - Attributes of the entities like price is an attribute of the product(entity) is referred here is an attribute. Value - A value of the attribute as $20 is a value for price attribute is referred here is a value.  Use of EAV Model EAV(Entity-Attribute-Value) is used to create new attributes of entities such as products, categories etc. With the use of eav models we don’t need to change the structure of the core tables of attributes thus it increases the scalability of the system.  Let’s have a look at how eav works in Magento2 -  Eav model used many several tables to store the data of the entity attributes. The top most table for the e
Post a Comment
Read more

Plugins in Magento2

Plugins in Magento2 Unlike Magento1, Magento2 introduces a whole new concept of Plugins or Interceptor. A plugin or interceptor is used to change the behaviour of the method of any class without affecting the actual class. This is a very powerful way to customize the core classes of Magento2.  Plugins are one of the customization methods in Magento2. In plugins, there is a design pattern called “Interception” which means “Inserting code dynamically without changing original class behaviour” and this is what plugins exactly do in Magento2. Plugins modify the behaviour of a plugin class function by intercepting a function call and adding code before, after and around that function’s call.  Plugins are used with public methods only.  Declaring Plugins To declare plugins in Magento2, we have to create di.xml according to the specific area.  Create di.xml inside Vendor/Module/etc for global.   < config >     < type name = "{ObservedType}" >       < plugin name
Post a Comment
Read more