Watch the screencast

Text Version

Step 1 – Adding the attachments

Adding attachments with the proper name is fundamental for this technique. We will append the language ISOs to the names, so that they can later be targeted in the template.

Login to the back office, then navigate to Catalog > Products, and choose one to start with. At the bottom of the Options tab, add two test attachments. The file names don’t matter, but the title you choose does. Add one attachment for each language it’s translated to, making sure you append the ISO code for that language after the name, like this: _en, _it, _fr.

Note: If you don’t know what the language code is, hop to International > Localization, and click on Languages. The ISO code is listed in the table:

If you need an attachment to display for all of the languages, make sure you do not add any language ISO to it.

Step 2 – Editing the template

For this tutorial I am using the “classic” template, that ships with PrestaShop 1.7. If you are using a custom theme, be aware that some of the code might be different, or even located in a different file.

Open up themes/classic/templates/catalog/product.tpl.

Locate the following code:

{if $product.attachments}
                    <div class="tab-pane fade in" id="attachments" role="tabpanel">
                       <section class="product-attachments">
                         <h3 class="h5 text-uppercase">{l s='Download' d='Shop.Theme.Actions'}</h3>

Right afterwards, but before the foreach loop, add the following

{$lang_checker = "_"|cat: {$language.iso_code}}
{$lang_checker_array = ['en', 'it']}

Make sure you use your own ISO codes instead of ‘en’ and ‘it’. Add all of the languages your store supports

Next, wrap the attachment block in the following IF statement

                         {if $attachment.name|strstr:{$lang_checker}}
                           <div class="attachment">
                             <h4><a href="{url entity='attachment' params=['id_attachment' => $attachment.id_attachment]}">{$attachment.name|replace:{$lang_checker}:''}</a></h4>
                             <p>{$attachment.description}</p
                             <a href="{url entity='attachment' params=['id_attachment' => $attachment.id_attachment]}">
                               {l s='Download' d='Shop.Theme.Actions'} ({$attachment.file_size_formatted})
                             </a>
                           </div>
{/if}

If you don’t need some attachments to display for all languages, you can go ahead and test it, as the basic part if basically done. If you do, you will need to add a little extra condition, and we will use that lang_checker_array for it.

Step 2.1 – Fallback for generic attachments

Right before the end of the IF statement that checks for our ISO code, add the following:

{else}
  {$denier = false}
  {foreach from=$lang_checker_array item=checkr_lang}
                              {if $attachment.name|strstr:{$checkr_lang}}
                              {$denier = true}
                              {/if}
  {/foreach}

Explanation: We are setting a variable (denier) that will prevent displaying the attachment if it contains any language ISO. Because of this logic, make sure you use a string that’s unique enough in case your attachment names contain product codes or alike, otherwise they won’t ever display.

Right afterwards, but still inside our main IF, add this last chunk of code

                               
{if !$denier}
<div class="attachment">
<h4><a href="{url entity='attachment' params=['id_attachment' => $attachment.id_attachment]}">{$attachment.name|replace:{$lang_checker}:''}</a></h4>
<p>{$attachment.description}</p
<a href="{url entity='attachment' params=['id_attachment' => $attachment.id_attachment]}">
{l s='Download' d='Shop.Theme.Actions'} ({$attachment.file_size_formatted})
</a>
</div>
{/if}

Which is basically a copy of the standard attachment code. If the attachment does not contain any iso code, it means we can display it normally.

We are done!

The post Creating Multilanguage attachments in PrestaShop 1.7 appeared first on NemoPS.

Watch the screencast

Text Version

If you have lots of users it might happen sometimes that a product goes out of stock while it’s in someone’s cart. For example two users add the last unit, one proceeds to the checkout and the other doesn’t. What happens is when the second customer places the order, the product will not be available anymore, and it will cause confusion if not irritation to that person, especially if you cannot restock that specific item.

The Cart Presenter in PrestaShop 1.7

The first file we need to edit is the cartPresenter, which is responsible of displaying cart information across the store.

Open up src/Adapter/Cart/cartpresenter.php and add the following around line 51, in the class properties:

private static $removedProducts = [];

Then locate the present method, and right after the following statement:

        if ($shouldSeparateGifts) {
            $rawProducts = $cart->getProductsWithSeparatedGifts();
        } else {
            $rawProducts = $cart->getProducts(true);
        }

Add this:

        // start nemo

        if(!self::$removedProducts)
            foreach ($rawProducts as $pk => $product)
            {
            // we want to remove the product in case it's not available
                if($product['quantity_available'] <= 0 && !Product::isAvailableWhenOutOfStock($product['out_of_stock']))
                {
                    Context::getContext()->cart->deleteProduct($product['id_product'],$product['id_product_attribute'], $product['id_customization'], $product['id_address_delivery']);
                    self::$removedProducts[] = $product['name'];
                    unset($rawProducts[$pk]);
                    continue;
                }
            }
           
        Context::getContext()->smarty->assign(['removed_products' => self::$removedProducts]);
        \Media::addJsDef(['removed_products' => self::$removedProducts]);

And that’s all for php! Before continuing let’s make sure the product actually gets removed, so let’s test it and see if they really get removed!

The shopping cart template in PrestaShop 1.7

Let’s open up themes/classic/modules/ps_shoppingcart/ps_shoppingcart.tpl

{if isset($removed_products) && $removed_products}
  <div id="removed-modal" class="modal">
    <div class="modal-dialog">
      <div class="modal-content">
        <div class="modal-body">
          <p>{l s='These products are out of stock' d='Shop.Theme.Checkout'}</p>
            <ul>
              {foreach from=$removed_products item='r_product'}
                <li>- {$r_product}</li>
              {/foreach}
            </ul>
            <p>{l s='And have therefore been removed from your cart' d='Shop.Theme.Checkout'}</p>
        </div>

      </div>
    </div>
  </div>
{/if}

And the very last thing is actually triggering the modal when we need, so let’s add some javascript to themes/classic/assets/js/custom.js

if(removed_products.length > 0) {
	$('#removed-modal').modal('show');
}

And that’s it! Now this modal doesn’t look so fancy, but no worries since in one of the next videos we will go over creating and styling custom popups in prestashop 1.7, so stay tuned!

The post Removing out of stock products from the cart in PrestaShop 1.7 appeared first on NemoPS.

Watch the screencast

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.

Watch the screencast

Text Version

METHOD 1 – Selectively enabling catalog mode

If we don’t need to display prices to our visitors, the simplest and quickest way to proceed is by selectively enable catalog mode. Open classes/controller/FrontController.php, and locate the following string, inside the init method:

'PS_CATALOG_MODE' => (bool)Configuration::get('PS_CATALOG_MODE') || (Group::isFeatureActive() && !(bool)Group::getCurrent()->show_prices),

Replace it with the following:

'PS_CATALOG_MODE' => $catalog_mode || (Group::isFeatureActive() && !(bool)Group::getCurrent()->show_prices),

We need to create that $catalog_mode variable of course, so let’s add this before the whole assign block:

$catalog_mode = (bool)Configuration::get('PS_CATALOG_MODE');
if(!$this->context->customer->id)
    $catalog_mode = true;

As you can see, we simply check if the customer id is set (that is, if the user is logged in) and if so, we set catalog mode to true, effectively disabling all cart functionalities. This however left us with a useless cart block, and without prices. Let’s see how to handle it differently then!

METHOD 2 – Selectively disable products

I will create an override for this one, so in override/classes, let’s create a new file named Product.php.

Let’s open it up, and copy over the construct method from the core product class. Get rid of everything inside it, and simply add the following:

Class Product extends ProductCore
{
    public function __construct($id_product = null, $full = false, $id_lang = null, $id_shop = null, Context $context = null)
    {
        parent::__construct($id_product, $id_lang, $id_shop);

        if(!Context::getContext()->customer->id)
            $this->available_for_order = false;
    }
}

This will take care of the product page. Now for the product list, the property is set elsewhere, and specifically in the getProductProperties method (without s). Copy the whole method from the original class again, but this time leave the content, and just append the following code at the end, right before self::$producPropertiesCache[$cache_key] = $row;

if(!$context->customer->id)
    $row['available_for_order'] = false;

And that’s all we need! Since we created a new override, remember it’s necessary to erase cache/class_index.php in order for the changes to take place.

The post Private Orders Shop in PrestaShop and thirty bees part 2: hide shopping options for visitors appeared first on NemoPS.

Watch the screencast

Text Version

I will use PrestaShop 1.6 for the demo but the modification works in thirty bees as well. Bear in mind it DOES NOT work in PrestaShop 1.7.

Open up controllers/front/AuthController.php

Look for the following code, around line 455. If it’s not in those whereabouts, just make sure you change every instance

$customer->active = 1;

set to 0, so that the user cannot perform any action right away.

Now we also want to give the user some feedback, so let’s redirect him to a custom page. Scroll down a few lines, and where you see all these redirects:

if (($back = Tools::getValue('back')) && $back == Tools::secureReferrer($back)) {
                            Tools::redirect(html_entity_decode($back));
                        }

And add a new one before

  Tools::redirect($this->context->link->getPageLink('welcome'));

Of course this page does not exist yet but we will create it in a moment.

Before that though, we have to take care of a little issue. Since the user has been created but set to inactive, the system treats it as banned by default. Even if we are to redirect to a page, we would instantly be kicked out of the session and redirected to the login. We want to create an exception so that the welcome page can be displayed.

Let’s go ahead and open up the customer class, so classes/customer.php
Look for the following method:

public static function isBanned($id_customer)

And at the very beginning, add:

        if(Context::getContext()->controller->php_self == 'welcome')
            return false;

That’s settled! Now for our welcome page, I will create a new controller and a template file in the theme folder

Let’s head to controllers/front, and create a new PHP file first, named WelcomeController.php:

class WelcomeControllerCore extends FrontController
{
    public $php_self = 'welcome';


    public function initContent()
    {
        parent::initContent();
        $this->setTemplate(_PS_THEME_DIR_.'welcome.tpl');
    }
}

Then in the theme folder, create a new file named welcome.tpl, adding the following code inside

{capture name="path"} {l s='Welcome'}{/capture}
<h1>{l s='Welcome to'} {$shop_name}! </h1>
<hr>
<p>
	{l s='Your account is currently under review, you will receive an email as soon as it is validated'}
</p>

So let’s go ahead and try it out now… but before let’s clear cache by erasing cache/class_index.php, since we added a new controller and the system wouldn’t read it otherwise.

The next step is to send out and email when a status is changed to active for the customer, in the back office.
Open controllers/admin/admincustomerscontroller.php

We will add a new method, which is inherited from the admincontroller class:

    public function processStatus()
    {
        if($object = parent::processStatus()) {
            if(get_class($object) == 'Customer' && $object->active) // the customer has been activated, send out an email
            {
                Mail::Send($object->id_lang, 'account_activated', $this->l('Your account has been activated'),
                    ['name' => $object->firstname .' '. $object->lastname],
                $object->email,
                $object->firstname .' '. $object->lastname,
                Configuration::get('PS_SHOP_EMAIL'),
                Configuration::get('PS_SHOP_NAME'));
            }
        }

       return $object;
    }

Of course, there is no such email template so we have to create it. I suggest copying an existing one, like the order confirmation, and adding new text, just to be quicker. The code is different for every template, just bear in mind to add the {name} variable inside it, so that the customer name is displayed!

This is it for part 1, make sure you test the email as well since sometimes they do fail for odd reasons, if you don’t see it coming, triple check the template names and make sure they are located in the proper path for each language you use.

In part two we will see how to prevent orders in case a customer is not registered, which is fundamental not to break the system if you have a one page checkout, as right now it would display an error.

The post Private Orders Shop in PrestaShop and thirty bees part 1: manual customer verification appeared first on NemoPS.

Watch the screencast

Text Version

To start with, open up global.js, located in your theme folder /js. At the very end, add the following:

$(document).ready(function() {
	if($('body').hasClass('category'))
	{
		$('.product_img_link').click(function(e) {
			$.totalStorage('last_visited_category', window.location.href);
		});
	}
});

Then, in product.tpl, again in the theme folder, find a proper spot for the button, then add the following inside a <script> tag:

	$(document).ready(function() {
		if(previous_category = $.totalStorage('last_visited_category'))
		{
			$('#goback').attr('href', previous_category);
			$.totalStorage('last_visited_category', '');
		} else $('#goback').hide();
	});

Right after id, add our button:

<a href="javascript:void(0)" class="btn btn-default" id="goback">
	<i class="icon-chevron-left left"></i> {l s='Go Back to the last category'}
</a>

Here is the final code for product.tpl

<script>

	$(document).ready(function() {
		if(previous_category = $.totalStorage('last_visited_category'))
		{
			$('#goback').attr('href', previous_category);
			$.totalStorage('last_visited_category', '');
		} else $('#goback').hide();
	});
</script>

<a href="javascript:void(0)" class="btn btn-default" id="goback">
	<i class="icon-chevron-left left">{l s='Go Back to the last category'}</i>
</a>

Notice: If you want to keep a record of the visited category across pages, you can remove $.totalStorage(‘last_visited_category’, ”); from the code in product.tpl.

The post How to create a “Go back to the category” button in PrestaShop and thirty bees appeared first on NemoPS.

Watch the screencast

The post Litespeed module for PrestaShop and thirty bees appeared first on NemoPS.

Watch the screencast

The post Setting up a staging site for PrestaShop and Thirtybees appeared first on NemoPS.

Watch the video guide

Core features

• Unlimited fields: Add as many new fields as you like
• Multiple input types: Choose between text, textarea or select box to perfectly fit the type of data you require from your customers
• Customizable format
• Choose if you want to display the fields in the back office list as well
• Multilanguage labels

The post New module: “Address Fields” just released! appeared first on NemoPS.

Watch the screencast

Duplicating product carriers in PrestaShop and ThirtyBees – text version

Create a new override in override/controllers/admin, and name it AdminProductsController.php:

class AdminProductsController extends AdminProductsControllerCore
{
}

We need to copy the original ProcessDuplicate method, and paste it into our override. You will see it’s calling a bunch of methods that start with “duplicate”. Add the following right after Product::duplicateSuppliers($id_product_old, $product->id):

            && Product::duplicateCarriers($id_product_old, $product->id)

Next, we have to add the method we are calling to the Product class. We will use another override, so let’s create Product.php in override/classes

Open it up, and paste the following, or if you have a product override already in place, just copy over the DuplicateCarriers method:

    public static function duplicateCarriers($id_product_old, $id_product_new)
    {
        $result = Db::getInstance()->executeS('
		SELECT *
		FROM `'._DB_PREFIX_.'product_carrier`
		WHERE `id_product` = '.(int)$id_product_old);

        foreach ($result as $row) {
            unset($row['id_product_carrier']);
            $row['id_product'] = $id_product_new;
            if (!Db::getInstance()->insert('product_carrier', $row)) {
                return false;
            }
        }

        return true;
    }	

Save, then reach the cache/ folder and erase class_index.php, so that the new overrides can get loaded in the system.

The post Duplicating Carriers along with Products in PrestaShop and ThirtyBees appeared first on NemoPS.