NemoPS » email

Blocking spam emails in PrestaShop

Nemo — Wed, 22 Aug 2018 02:11:43 +0000

As you know PrestaShop has been dreaded by a lot of spam issues recently. In this video we will see how to quickly block spam emails coming from the PrestaShop contact form

Watch the screencast

Subscribe Post Scriptum's Youtube Channel

Let’s get started! Create a new php file in the override/controllers/front folder, and name it: ContactController.php and add the following inside php tags:


class ContactController extends ContactControllerCore
{
}

We need to latch into the postProcess method, so let’s extend it:

public function postProcess()
{
    if(Tools::isSubmit('submitMessage'))
    {
    }
}

We want to save the submitted message to a variable first, and then the email:

    	$message = Tools::getValue('message');
        $from = trim(Tools::getValue('from'))

Now to keep things tidy we will create two new arrays, one will contain the list of strings to ban from emails, the other the ones to ban from the content:


            $banned_in_email = ['.ru', 'qq.com', '.vn'];
            $banned_content = ['email marketing'];

Please Note: make sure you use strings that are related to the spam you are actually getting. I am getting spam from .ru, qq.com and .vn domains, so that’s what I am blocking. I also get a lot of emails containing “email marketing” in the text, and am unlikely to get anything real with that type of content.
Make sure you do not ban real customers!

We want to loop through both and spawn an error if anything is contained in the submitted variables:

            foreach ($banned_in_email as $string) {
                if(strstr($from, $string))
                    $this->errors[] = Tools::displayError('This email address is not allowed');
            }
            foreach ($banned_content as $string) {
                if(strstr($message, $string))
                    $this->errors[] = Tools::displayError('Invalid content');
            }

And that’s basically it, we just need to call the parent at the very end of the method:

parent::postProcess();

And we are done! Here is the complete override:

class ContactController extends ContactControllerCore
{
    public function postProcess()
    {
        if(Tools::isSubmit('submitMessage')) {

            $message = Tools::getValue('message');
            $from = Tools::getValue('from');

            $banned_in_email = ['.ru', 'qq.com', '.vn'];
            $banned_content = ['email marketing'];

            foreach ($banned_in_email as $string) {
                if(strstr($from, $string))
                    $this->errors[] = Tools::displayError('This email address is not allowed');
            }

            foreach ($banned_content as $string) {
                if(strstr($message, $string))
                    $this->errors[] = Tools::displayError('Invalid Content');
            }
        }
        parent::postProcess();
    }
}

Before you test, make sure you erase cache/class_index.php, so that the new override is loaded in the system.

The post Blocking spam emails in PrestaShop appeared first on NemoPS.

Custom E-Mail Configuration in PrestaShop (GMail)

Nemo — Thu, 26 May 2016 09:08:26 +0000

In this PrestaShop Tutorial, we sill see how to configure E-Mails with custom SMTP settings, specifically using Gmail with PrestaShop

Watch the Screencast

Subscribe Post Scriptum's Youtube Channel

The post Custom E-Mail Configuration in PrestaShop (GMail) appeared first on NemoPS.

Get email notifications for new customers registrations

Nemo — Mon, 05 Jan 2015 11:38:16 +0000

In this quick tip we will see how to enable email notifications for when a new client registers to our shop.

The Plan

Since we want to be informed when a new user registers, we need to add our code snippets right where the user itself is notified about it. For this reason, we will be extending the sendConfirmationMail method of the AuthController.php file, and create a new email template as well.

The AuthController override

As always it’s good practice to use overrides instead of modifying core files directly (to preserve changes after updates). Therefore, create a new file called AuthController.php inside override/controllers/front. Inside php tags, paste the following override code:

Class AuthController extends AuthControllerCore
{

	
}

As mentioned above, we need to extend the default sendConfirmationMail method, so let’s grab it from the original controller and paste it inside our override (this is from Prestashop 1.6.0.9):

Class AuthController extends AuthControllerCore
{
	protected function sendConfirmationMail(Customer $customer)
	{
		if (!Configuration::get('PS_CUSTOMER_CREATION_EMAIL'))
			return true;

		return Mail::Send(
			$this->context->language->id,
			'account',
			Mail::l('Welcome!'),
			array(
				'{firstname}' => $customer->firstname,
				'{lastname}' => $customer->lastname,
				'{email}' => $customer->email,
				'{passwd}' => Tools::getValue('passwd')),
			$customer->email,
			$customer->firstname.' '.$customer->lastname
		);
	}
	
}

Just in case, let’s make sure emails still work. Erase the class_index.php located in the cache/ folder. Then, try registering a new user and make sure you get the confirmation email. If you do, it’s time to add another rule to inform the admin; right before the return, add:

Mail::Send(
			Configuration::get('PS_LANG_DEFAULT'),
			'account_for_admin',
			Mail::l('New client!'),
			array(
				'{firstname}' => $customer->firstname,
				'{lastname}' => $customer->lastname,
				'{email}' => $customer->email
				),
			Configuration::get('PS_SHOP_EMAIL'),
			Configuration::get('PS_SHOP_NAME')
		);

Explanation: we just copied the returned code and adapted it to our needs; first, instead of using the customer language to grab the email template, we use the shop’s default one. This way we don’t need to create multiple/translated templates. Then, we pass in ‘account_for_admin’ as email template name; it doesn’t exist yet so don’t try running a new registration or it won’t work. Then, to preserve the user’s credentials we get rid of the password. Lastly we set the “to” parameter to the shop’s email, and set the receiver to the shop’s name. That’s all there is to it. Let’s now create that template.

Creating a new email template

Instead of proceeding from scratch, I generally copy an existing html template, to have them all uniform. Let’s use that user welcome as base. Reach mails/en (or whatever your default language’s ISO is, you can check it in the back office, localization, languages); Clone both account.html and account.txt, and then rename them to account_for_admin.html and account_for_admin.txt. Open up the .txt file, it will look something like:



[{shop_url}] 

Hi {firstname} {lastname},

Thank you for creating a customer account at {shop_name}. 

Here are your login details:

E-MAIL ADDRESS: {email}

PASSWORD: {passwd} 		 

Important Security Tips:

* Always keep your account details safe.

* Never disclose your login details to anyone.

* Change your password regularly.

* Should you suspect someone is using your account illegally, please
notify us immediately.

You can now place orders on our shop: {shop_name}
[{shop_url}] 

{shop_name} [{shop_url}] powered by
PrestaShop(tm) [http://www.prestashop.com/]

Let’s modify it so to fit our needs:



[{shop_url}] 

Hi!

A new customer just signed up for an account at {shop_name}. 

Here are the details:

E-MAIL ADDRESS: {email}

NAME: {firstname} {lastname}

Then, apply the same modifications to the html file (please note I am only copying relevant parts of the template):



	
		
			Hi {firstname} {lastname},

			Thank you for creating a customer account at {shop_name}.



	
		
			Hi!

			A new customer just signed up for an account at {shop_name}.

Then



	
		
			
				 
				
					
						
							Your {shop_name} login details						
						
							Here are your login details:
 
							E-mail address: {email}

							Password: {passwd}



	
		
			
				 
				
					
						
							Your {shop_name} login details						
						
							Here are your login details:
 
							E-mail address: {email}

							Password: {passwd}

Lastly, you can get rid of this:


	 


	
		
			
				 
				
					
						Important Security Tips:
						
							Always keep your account details safe.
							Never disclose your login details to anyone.
							Change your password regularly.
							Should you suspect someone is using your account illegally, please notify us immediately.
						
					
				
				 
			
		
	


	 


	
		
			You can now place orders on our shop: {shop_name}
		
	


						
							 
						
						
							
								{shop_name} powered by PrestaShop™

And it’s done! Time to test the outcome!

Troubleshooting

When dealing with emails and Prestashop, there is a high chance of failure. Don’t be discouraged if if doesn’t work at the first attempt, and check the following:

- Send out a test email from advanced parameters -> emails to your mail address
- Make sure it didn’t end up in the spam folder
- Double-check the new template name, it must be account_for_admin everywhere
- Make sure you added the template to the correct iso folder. If unsure, clone it to every of them

If you still don’t receive the email, it’s worth trying to kill the Mail::Send method in case of failure, by using the following code instead:

Mail::Send(
			Configuration::get('PS_LANG_DEFAULT'),
			'account_for_admin',
			Mail::l('New client!'),
			array(
				'{firstname}' => $customer->firstname,
				'{lastname}' => $customer->lastname,
				'{email}' => $customer->email
				),
			Configuration::get('PS_SHOP_EMAIL'),
			Configuration::get('PS_SHOP_NAME'),
			null,null,null,null,_PS_MAIL_DIR_,true
		);

The last parameter I passed in is telling the method to die in case of failure. If that happens, you should be given more info about what went wrong.

The post Get email notifications for new customers registrations appeared first on NemoPS.

How to enable email notifications for Product Comments in Prestashop

Nemo — Mon, 14 Apr 2014 10:08:53 +0000

If you have a solid and active customer base, it is frustrating to go and check the Product Comments module every day just to know if a new review has been posted. Let’s see how to add email notifications for comments!

Download Project Files

Compatibility: Prestashop 1.5, Prestashop 1.6
Version used: Prestashop 1.6

Introduction

Although I will be using Prestashop 1.6’s code for this tutorial, you can apply the same process to the Prestashop 1.5 version of the product comments module. Just be aware that you will have to use a 1.5 email template instead of copying the 1.6 one I will use here, to have all your emails uniform, if needed.

There is a small thing to notice: no language variable is passed when a new comment is added via ajax. This means we will create a new email template for the default shop language only, as, for the time being, I have found no reliable way to create a multilanguage-enabled function for this.

We will be amending one file only throughout the tutorial: default.php, along with creating two new email templates in the main mails/*language* folder. Let’s get started!

The default Comments controller

Prestashop comments’ submission is handled through an ajax call, so that no page refresh is needed when adding a new one. The main php file beneath all the comment submission process is default.php, and can be found in modules/productcomments/controllers/front/. Open it up in your favorite code editor, then locate the ajaxProcessAddComment() method.

This function is called upon comment submission, and it’s the place where we need to add our email send-out.

	protected function ajaxProcessAddComment()
	{
		$module_instance = new ProductComments();

		$result = true;
		$id_guest = 0;
		$id_customer = $this->context->customer->id;
		if (!$id_customer)
			$id_guest = $this->context->cookie->id_guest;

		$errors = array();
		// Validation
		if (!Validate::isInt(Tools::getValue('id_product')))
			$errors[] = $module_instance->l('ID product is incorrect', 'default');
		if (!Tools::getValue('title') || !Validate::isGenericName(Tools::getValue('title')))
			$errors[] = $module_instance->l('Title is incorrect', 'default');
		if (!Tools::getValue('content') || !Validate::isMessage(Tools::getValue('content')))
			$errors[] = $module_instance->l('Comment is incorrect', 'default');
		if (!$id_customer && (!Tools::isSubmit('customer_name') || !Tools::getValue('customer_name') || !Validate::isGenericName(Tools::getValue('customer_name'))))
			$errors[] = $module_instance->l('Customer name is incorrect', 'default');
		if (!$this->context->customer->id && !Configuration::get('PRODUCT_COMMENTS_ALLOW_GUESTS'))
			$errors[] = $module_instance->l('You must be logged in order to send a comment', 'default');
		if (!count(Tools::getValue('criterion')))
			$errors[] = $module_instance->l('You must give a rating', 'default');

		$product = new Product(Tools::getValue('id_product'));
		if (!$product->id)
			$errors[] = $module_instance->l('Product not found', 'default');

		if (!count($errors))
		{
			$customer_comment = ProductComment::getByCustomer(Tools::getValue('id_product'), $id_customer, true, $id_guest);
			if (!$customer_comment || ($customer_comment && (strtotime($customer_comment['date_add']) + (int)Configuration::get('PRODUCT_COMMENTS_MINIMAL_TIME')) < time()))
			{

				$comment = new ProductComment();
				$comment->content = strip_tags(Tools::getValue('content'));
				$comment->id_product = (int)Tools::getValue('id_product');
				$comment->id_customer = (int)$id_customer;
				$comment->id_guest = $id_guest;
				$comment->customer_name = Tools::getValue('customer_name');
				if (!$comment->customer_name)
					$comment->customer_name = pSQL($this->context->customer->firstname.' '.$this->context->customer->lastname);
				$comment->title = Tools::getValue('title');
				$comment->grade = 0;
				$comment->validate = 0;
				$comment->save();

				$grade_sum = 0;
				foreach(Tools::getValue('criterion') as $id_product_comment_criterion => $grade)
				{
					$grade_sum += $grade;
					$product_comment_criterion = new ProductCommentCriterion($id_product_comment_criterion);
					if ($product_comment_criterion->id)
						$product_comment_criterion->addGrade($comment->id, $grade);
				}

				if (count(Tools::getValue('criterion')) >= 1)
				{
					$comment->grade = $grade_sum / count(Tools::getValue('criterion'));
					// Update Grade average of comment
					$comment->save();
				}
				$result = true;

				Tools::clearCache(Context::getContext()->smarty, $this->getTemplatePath('productcomments-reviews.tpl'));
			}
			else
			{
				$result = false;
				$errors[] = $module_instance->l('You should wait').' '.Configuration::get('PRODUCT_COMMENTS_MINIMAL_TIME').' '.$module_instance->l('seconds before posting a new comment');
			}
		}
		else
			$result = false;

		die(Tools::jsonEncode(array(
			'result' => $result,
			'errors' => $errors
		)));
	}

It would be useless to send an email notification if the comment submission process failed; thus, we will insert our code right after that $result = true; declaration.

So, right before Tools::clearCache(Context::getContext()->smarty, $this->getTemplatePath(‘productcomments-reviews.tpl’)); add:

				// send out an email! by Nemo

				$product_name = Product::getProductName($comment->id_product);
				$shop_email = Configuration::get('PS_SHOP_EMAIL');
				$shop_name = Configuration::get('PS_SHOP_NAME');

				Mail::Send(Configuration::get('PS_LANG_DEFAULT'), 'new_comment', Mail::l('New comment added'),
				array(
					'{comment_content}' => $comment->content,
					'{product_name}' => $product_name
				), $shop_email,
					$shop_name, $shop_email);

Explanation: first off, we need some variables. We get the product name, to print out more information in the email, then the shop name and email to be used as arguments of the Mail::Send function. This very same method is really simple:

We pass the default language to it, then the name of the template we need (which doesn’t exist yet at this stage, but we will be creating it shortly), then the email Title. As template variables, we want ourselves to be aware of the content of the comment, as well as the product concerned. Lastly, we set the shop email as sender, receiver, and the shop name as receiver’s name.

We are done with this file already. Let’s create the actual email templates!

Creating the new email templates

This is the easiest part. Two files are needed in order for email notifications to work in Prestashop: an .html version, and a .txt one. Reach the main mails/ folder, and inside it access the subfolder with your default store language’s ISO code. Then, create a new file called new_comment.html and paste the following inside:



	
		
		
		Message from {shop_name}
		

		

	
	
		
			
				 
				
					
						
							
								
									
								
							
						


	
		
			Hi!
		
	


	 


	
		
			
				 
				
					
						
							You have received a new comment for the product "{product_name}"						
						
							{comment_content}
						
					
				
				 
			
		
	


						
							 
						
						
							
								{shop_name} powered by PrestaShop™

Then create another one named new_comment.txt, and paste this inside:


[{shop_url}] 

Hi!,

You have received a new comment for the product "{product_name}"

{comment_content}
{shop_name} [{shop_url}] powered by
PrestaShop(tm) [http://www.prestashop.com/]

NOTE: If you are using Prestashop 1.6 you can simply copy and paste the above inside a .html and .txt file, otherwise, if you are trying to apply it to 1.5, my suggestion is to pick a default email template, such as the log_alert one, and modify it accordingly by adding the new variables.

We are done! Save, and then test the new email notifications out by adding a comment!

Final Notes

If your emails are not being sent out, make sure you test them by going to Advanced Parameters, E-Mail in the back office. Double check our email settings and try sending out a test email as well.

If everything works at this state, inspect the ajax call by accessing the network tab in a browser console (F12 on Chrome, for example). The comment ajax call looks like default?action=add_comment&secure_key=6efb5690f08b14a4d0c050119418fc68&rand=1397469373235.

The post How to enable email notifications for Product Comments in Prestashop appeared first on NemoPS.

Forbid the usage of junk-alias emails in Prestashop

Nemo — Wed, 12 Mar 2014 10:17:55 +0000

If you want your customers to use a valid email address, you might want to forbid the use of expiring aliases. Let’s create a module to handle this validation!

Download Project Files

Version used: Prestashop 1.5.6.2
Compatibility: Prestashop 1.5, Prestashop 1.6

Introduction

Depending on your market, a certain percentage of your clients might be using junk email aliases when registering or checking out as guests on your site. If you strive to keep a solid customer base, and especially if you want to fidelize them, this might become a real issue at a certain point. Therefore, you want to make sure they use at least a valid, non-junk/alias address on your site.

The issue can easily be solved with the use of action Hooks. Prestashop handles address validation through the so-called “AuthController”, and wisely comes with an action hook right at the beginning of the method used to process a new account (be it guest or not) creation.

In today’s tutorial, we will create a small, lightweight module that hooks to actionBeforeSubmitAccount, so we can target any keyword we dislike, and prevent its usage within the email address field. Let’s get to it!

Step 1 – Creating the Prestashop Module and the back office interface

In order to make things easier for us, we will create a back office interface that saves all these words in a single database configuration entry. This way, whenever we feel like adding a new “banner keyword” for the email address field, we can simply reach out the module’s configuration page, add it and save.

Let’s start by adding a new, simple module. Download the project files, grab the emailchecker folder that you find inside the ‘start_here’ folder, and drop it inside your modules/ folder.

Open up emailchecker.php, then modify the install() method by registering the new hook, as follows:

	public function install()
	{
		if (!parent::install() OR			
			!$this->registerHook('actionBeforeSubmitAccount'))
			return false;
		return true;
	}

actionBeforeSubmitAccount is the name of the hook we want to target.

Then, let’s create the markup to handle banned keywords from the back office. Inside the _displayForm() method, add the following:

		$this->_html .= '
			
				_path.'logo.gif" alt="" title="" />'.$this->l('Settings').'
		';

		$this->_html .='
					'.$this->l('Banned keywords').'
					
						
					
					
		';

		/* Submit button */
		$this->_html .='';


		$this->_html .= '
				
			';

It’s a regular, simple form. If you are not used to creating Prestashop Modules, you might want to have a look at how to create a prestashop module in the official Prestashop Documentation.

Briefly: we added a new field to hold the banned keywords. We will add them in the input one by one, separated by comma. Then, we will save them inside the PS_EMAIL_BANNED_KEYWORDS, and this very same value will be displayed, if set, each time we access the form.

At this point, let’s save the entries to the configuration table. Edit the _postProcess() method as follows:

	private function _postProcess()
	{
		if (Tools::isSubmit('submitKw')) // handles the basic config update
		{
			Configuration::updateValue('PS_EMAIL_BANNED_KEYWORDS', Tools::getValue('bannedkw'));
			$this->_html .= $this->displayConfirmation($this->l('Keywords updated'));
		}
	}

We don’t really need validation, but feel free to add it if you want to make sure data is entered correctly here (words separated by commas, so Regular Expressions will come in handy).

As a last thing, if you want to make sure no trace is left into the database upon the module’s removal, erase the configuration entry by editing the uninstall method:

public function uninstall()
	{
		if (!parent::uninstall() OR !Configuration::deleteByName('PS_EMAIL_BANNED_KEYWORDS'))
			return false;
		return true;
	}

We are done with the back office! Time to install the module. Reach out the modules panel in the back office, look for emailchecker and install it. Test the configuration page and make sure you can save keywords properly. Once this is settled, move to the next step!

Validating the email address

It’s time to create the hook method that will handle email validation. Inside our module’s php file, create a new method named hookActionBeforeSubmitAccount:

	public function hookActionBeforeSubmitAccount($params)
	{
	}

Let’s first grab our keywords:

	public function hookActionBeforeSubmitAccount($params)
	{
		
		$banned_keywords = Configuration::get('PS_EMAIL_BANNED_KEYWORDS');
		if(!$banned_keywords)
			return;

	}

If nothing is found for that configuration entry, return, as there is nothing to do. Otherwise, explode the keywords string using the comma separator, and iterate through them using a foreach:


	public function hookActionBeforeSubmitAccount($params)
	{
		
		$banned_keywords = Configuration::get('PS_EMAIL_BANNED_KEYWORDS');
		if(!$banned_keywords)
			return;
		// explode keywords by comma
		$kw = explode(',', $banned_keywords);
		foreach ($kw as $k) {
			
		}

		return;
	}

Finally, let’s check the presence of our banned keyword inside the email address. There are several methods to do this. The easiest one is using the strstr function of PHP. Of course, you might as well use regular expressions if you feel more comfortable with it:


	public function hookActionBeforeSubmitAccount($params)
	{
		
		$banned_keywords = Configuration::get('PS_EMAIL_BANNED_KEYWORDS');
		if(!$banned_keywords)
			return;
		// explode keywords by comma
		$kw = explode(',', $banned_keywords);
		foreach ($kw as $k) {
			if (strstr(strtolower(Tools::getValue('email')), strtolower($k))) {
				$this->context->controller->errors[] = Tools::displayError('Invalid email address');
			}
		}

		return;
	}

We are telling the script: if the keyword is found inside the email address (if it’s a substring of it, grabbed using the helper getValue, which retrieves $_POST and $_GET data) add and error to the current controller. Since the current controller is authController, the information validation will not proceed, and nothing will be added to the database. This happens because Prestashop checks the size of the errors array right before adding data to the store.

Save and test everything out. If it works properly, you should see the message popping out as soon as you try to register using an address containing the banner keyword. This will work for both the standalone account creation, registered client checkout, and guest checkout (both 5-steps and one page).

Conclusion

Validating the email address is a very limited usage of the ActionBeforeSubmitAccounthook. You can validate all data sent via $_POST using the account creation form with it. Here is the complete array, take from Prestashop 1.5.6.2:

'id_gender' => string '1' (length=1)
  'customer_firstname' => string 'Fabio' (length=6)
  'customer_lastname' => string 'Porta' (length=6)
  'email' => string 'something@mailexpire.com' (length=23)
  'passwd' => string 'mypassw' (length=7)
  'days' => string '' (length=0)
  'months' => string '' (length=0)
  'years' => string '' (length=0)
  'referralprogram' => string '' (length=0)
  'email_create' => string '1' (length=1)
  'is_new_customer' => string '1' (length=1)
  'back' => string 'my-account' (length=10)
  'submitAccount' => string 'Register' (length=8)

The post Forbid the usage of junk-alias emails in Prestashop appeared first on NemoPS.