NemoPS » prestashop 1.7

Creating Multilanguage attachments in PrestaShop 1.7

Nemo — Wed, 05 Dec 2018 13:24:30 +0000

Attachments are a great way to provide your customers with rich pre-sale information about your products. But what if your site is multilingual? Let’s see how to make Attachments multilanguage in PrestaShop 1.7.

Watch the screencast

Subscribe Post Scriptum's Youtube Channel

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}
                    
                       
                         {l s='Download' d='Shop.Theme.Actions'}

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}}
                           
                             {$attachment.name|replace:{$lang_checker}:''}
                             {$attachment.description}
                               {l s='Download' d='Shop.Theme.Actions'} ({$attachment.file_size_formatted})
                             
                           
{/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}

{$attachment.name|replace:{$lang_checker}:''}
{$attachment.description}
{l s='Download' d='Shop.Theme.Actions'} ({$attachment.file_size_formatted})


{/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.

Removing out of stock products from the cart in PrestaShop 1.7

Nemo — Thu, 04 Oct 2018 00:08:07 +0000

PrestaShop 1.7 does not remove out of stock products from shopping carts, creating major troubles when keeping low stock. Let’s see how to improve our customer’s experience with a simple modification!

Watch the screencast

Subscribe Post Scriptum's Youtube Channel

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}
  
    
      
        
          {l s='These products are out of stock' d='Shop.Theme.Checkout'}
            
              {foreach from=$removed_products item='r_product'}
                - {$r_product}
              {/foreach}
            
            {l s='And have therefore been removed from your cart' d='Shop.Theme.Checkout'}
        

      
    
  
{/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.

Creating a “Clear cart” button in PrestaShop 1.7

Nemo — Mon, 06 Nov 2017 13:09:06 +0000

Let’ see how to create a button to empty the PrestaShop 1.7 shopping cart in one click!

Version used: Prestashop 1.7.2.4

In this tutorial we will see how to apply my previous guide on Creating a “Clear cart” button in PrestaShop to PrestaShop 1.7, as it doesn’t work out of the box because of the new template.

The basic code still works, and the process is more or less the same, though the files needing modifications are totally different. For this tutorial, I will be using the classic (or standard) template, so wherever you read “themename”, just put classic. As a side not, please notice some files might be different if you use a custom PrestaShop theme.

Adding the button to the cart page in PrestaShop 1.7

The PrestaShop 1.7 template structure is quite different from 1.6, so we need to account for that. The main view for the cart is now located at themes/*themename*/templates/checkout/, and it’s called cart.tpl. Open it up, and locat the following block:

      {block name='cart_overview'}
        {include file='checkout/_partials/cart-detailed.tpl' cart=$cart}
      {/block}

This represents the products list block, and we want to add the button right after it:

    
      Empty Cart

At this point, unlike 1.6 where we could add our code directly to the template, with PrestaShop 1.7 we have to use a new file, named custom.js.

Adding new javascript to a PrestaShop 1.7 template

Open up custom.js, located in themes/*themename*/assets/js.
It’s empty by default, so if not (as in the case of custom templates), just add the code at the end.

This file is loaded on all pages, and since we only want to run it on the cart one, we have to wrap our snippet with a condition:

if(prestashop.page.page_name == 'cart')
{}

The prestashop javascript variable is a new global available in all pages of the shop, which contains a number of useful data that can be used in scripts. In this case, we use the current page name.

Here is all the rest of the code we need:

$(document).ready(function() {

	    $('#removeAll').click(function(e) {
	        e.preventDefault()
	        $.ajax({
	            type: 'POST',
	            headers: { "cache-control": "no-cache" },
	            url: prestashop.urls.base_url + "cart",
	            async: true,
	            cache: false,
	            data: 'deleteAll=1&token=' + prestashop.token + '&ajax=true',
	            success: function(data){	
	                window.location.reload();
	            }
	        })
	    });
	});

Explanation: we are using the prestashop variable again, this time to fetch the base url. The cart controller, which we will be editing shortly, can be accessed at /cart by default, so we pass this url to the ajax call.
For the querystring, we pass in deleteAll, to make sure we can refer to this action in the next step, a token required by PrestaShop 1.7, and ajax=true, so that the cart know the action has to be run in ajax mode.
If the call is successful, we refresh the page to show that the cart is now empty.

Editing the CartController

PrestaShop 1.7 discourages the use of overrides, but we will use one in any case
Create a new file in override/controllers/front, and name it cartController.php. Reach back the original cart controller in the main controllers/front, and copy the whole updateCart method, pasting it into our new file:

    protected function updateCart()
    {
        // Update the cart ONLY if $this->cookies are available, in order to avoid ghost carts created by bots
        if ($this->context->cookie->exists() && !$this->errors && !($this->context->customer->isLogged() && !$this->isTokenValid())) {
            if (Tools::getIsset('add') || Tools::getIsset('update')) {
                $this->processChangeProductInCart();
            } elseif (Tools::getIsset('delete')) {
                $this->processDeleteProductInCart();
            } elseif (CartRule::isFeatureActive()) {
                if (Tools::getIsset('addDiscount')) {
                    if (!($code = trim(Tools::getValue('discount_name')))) {
                        $this->errors[] = $this->trans('You must enter a voucher code.', array(), 'Shop.Notifications.Error');
                    } elseif (!Validate::isCleanHtml($code)) {
                        $this->errors[] = $this->trans('The voucher code is invalid.', array(), 'Shop.Notifications.Error');
                    } else {
                        if (($cartRule = new CartRule(CartRule::getIdByCode($code))) && Validate::isLoadedObject($cartRule)) {
                            if ($error = $cartRule->checkValidity($this->context, false, true)) {
                                $this->errors[] = $error;
                            } else {
                                $this->context->cart->addCartRule($cartRule->id);
                            }
                        } else {
                            $this->errors[] = $this->trans('This voucher does not exist.', array(), 'Shop.Notifications.Error');
                        }
                    }
                } elseif (($id_cart_rule = (int)Tools::getValue('deleteDiscount')) && Validate::isUnsignedId($id_cart_rule)) {
                    $this->context->cart->removeCartRule($id_cart_rule);
                    CartRule::autoAddToCart($this->context);
                }
            }
        } elseif (!$this->isTokenValid() && Tools::getValue('action') !== 'show' && !Tools::getValue('ajax')) {
            Tools::redirect('index.php');
        }
    }

All we have to do now is add our condition, as part of all those ELSEIFs:

            elseif (Tools::getIsset('deleteAll')) {
                $this->context->cart->delete();
                $this->context->cookie->id_cart = 0;
                die(1);
            }

Here is the final code:

    protected function updateCart()
    {
        // Update the cart ONLY if $this->cookies are available, in order to avoid ghost carts created by bots
        if ($this->context->cookie->exists() && !$this->errors && !($this->context->customer->isLogged() && !$this->isTokenValid())) {
            if (Tools::getIsset('add') || Tools::getIsset('update')) {
                $this->processChangeProductInCart();
            } elseif (Tools::getIsset('delete')) {
                $this->processDeleteProductInCart();

            } elseif (Tools::getIsset('deleteAll')) { /* Nemo */
                $this->context->cart->delete();
                $this->context->cookie->id_cart = 0;
                die(1);
            } elseif (CartRule::isFeatureActive()) {
                if (Tools::getIsset('addDiscount')) {
                    if (!($code = trim(Tools::getValue('discount_name')))) {
                        $this->errors[] = $this->trans('You must enter a voucher code.', array(), 'Shop.Notifications.Error');
                    } elseif (!Validate::isCleanHtml($code)) {
                        $this->errors[] = $this->trans('The voucher code is invalid.', array(), 'Shop.Notifications.Error');
                    } else {
                        if (($cartRule = new CartRule(CartRule::getIdByCode($code))) && Validate::isLoadedObject($cartRule)) {
                            if ($error = $cartRule->checkValidity($this->context, false, true)) {
                                $this->errors[] = $error;
                            } else {
                                $this->context->cart->addCartRule($cartRule->id);
                            }
                        } else {
                            $this->errors[] = $this->trans('This voucher does not exist.', array(), 'Shop.Notifications.Error');
                        }
                    }
                } elseif (($id_cart_rule = (int)Tools::getValue('deleteDiscount')) && Validate::isUnsignedId($id_cart_rule)) {
                    $this->context->cart->removeCartRule($id_cart_rule);
                    CartRule::autoAddToCart($this->context);
                }
            }
        } elseif (!$this->isTokenValid() && Tools::getValue('action') !== 'show' && !Tools::getValue('ajax')) {
            Tools::redirect('index.php');
        }
    }

We are done! Reach the back office, Advanced Parameters, Performance, and hit the clear cache button on the top right, so that the override takes place.

Should it not work, check that Disable all overrides is set to no, right below on the same page. If it still doesn’t, try editing the core CartController.php.

The post Creating a “Clear cart” button in PrestaShop 1.7 appeared first on NemoPS.

Manufacturers in alphabetical list in PrestaShop 1.7

Nemo — Tue, 07 Feb 2017 11:50:04 +0000

As we did for PrestaShop 1.5, let’s see how to turn the boring manufacturer list into an alphabetical, fancy one, for PrestaShop 1.7

Subscribe Post Scriptum's Youtube Channel

Full Code to display manufacturers in an alphabetical list

 
      
      
        #
        A
        B
        C
        D
        E
        F
        G
        H
        I
        J
        K
        L
        M
        N
        O
        P
        Q
        R
        S
        T
        U
        V
        W
        X
        Y
        Z        
      

  
      
          {$current_letter = '#'}
          {foreach from=$brands item=brand}
            {$first_letter = $brand.name|substr:0:1}
            {if $current_letter != $first_letter}
              {if !$first_letter|in_array:['0','1','2','3','4','5','6','7','8','9']}
                {$current_letter = $first_letter|upper}
                
              
              {/if}
              
              
                {$current_letter|upper}
                
            {/if}
            
              {$brand.name}
            
          {/foreach}



.all-brands .letter-select li {
	float:left;
}

.all-brands .letter-select a {
	padding: 11px;
	font-weight: bold;
	font-size: 14px;
	display:block;
}

.all-brands .box-letter .box-title {
	width: 100%;
	display:block;
	background: #ccc;
	font-weight: bold;
	height: 40px;
	line-height: 40px;
	padding-left: 10px
}

.all-brands .box-letter .letter-content {
	line-height: 32px;
	padding-left: 10px
}

.all-brands .box-letter p {
	margin-bottom: 0;
	float: left;
	width: 25%;
}

The post Manufacturers in alphabetical list in PrestaShop 1.7 appeared first on NemoPS.

Adding images to the top menu in PrestaShop 1.7

Nemo — Tue, 17 Jan 2017 11:42:39 +0000

In this tutorial we will take back images for the PrestaShop top menu, that had been removed in 1.7

Subscribe Post Scriptum's Youtube Channel

The post Adding images to the top menu in PrestaShop 1.7 appeared first on NemoPS.

Adding subcategories to the category page in PrestaShop 1.7

Nemo — Mon, 02 Jan 2017 11:48:34 +0000

Have you been troubled by the absence of subcategories, in PrestaShop 1.7’s category pages? Let’s take them back in a few, simple steps!

Long time PrestaShop users have always been able to display subcategories in category pages, whatever theme they used. However, for some reason PrestaShop 1.7 doesn’t seem to have any subcategory showing on page with the classic (standard) theme, making it harder for users to navigate through the catalog, if the merchant chose not to use the side category block or layered navigation. Taking them back is fortunately easy enough, and can be done by almost just cloning the code from the 1.6 default-bootstrap template.
The files we need to edit are category.tpl and theme.css, so let’s get to it!

Adding the subcategories loop to PrestaShop 1.7’s category template

In the classic theme, let’s open up category.tpl, located in themes\classic\templates\catalog\listing, it should look like the following:

{extends file='catalog/listing/product-list.tpl'}

{block name='product_list_header'}
    
      {$category.name}
      {if $category.description}
        {$category.description nofilter}
        
          
        
      {/if}
    
    
      {$category.name}
    
{/block}

What we want to do is append the subcategory loop inside the block, just before it closes, so after the div containing the category title. The $subgcategories variable is already assigned to the template, much like in PrestaShop 1.6, and it’s ready to be used:



  {l s='Subcategories'}
  
  	{foreach from=$subcategories item=subcategory}
  	{$subcategory.name}
	{/foreach}

The code we just added is pretty much useless at this stage, as it just prints out each subcategory’s name, but let’s first see if it works. Save and refresh any category having children, and subcategories should pop up like this:

Nice! Let’s not make our effort useful by linking them to the proper pages



  {l s='Subcategories'}
  
  	{foreach from=$subcategories item=subcategory}
  	
  		{$subcategory.name|truncate:25:'...'|escape:'html':'UTF-8'}
  	
	{/foreach}

Explanation: I copied and pasted the code from 1.6 for the category title, simply wrapping the name in an h5 tag, then an anchor pointing to the proper page. To get the url, we can still use the $link class, and its getCategoryLink method. I also left in the truncate modifier for the name, which cuts it to the length of 25 characters, and lastly escaped it.

At this point they are at least useful! But why don’t we go ahead and add the image as well? Let’s do it right before the h5:



  {l s='Subcategories'}
  
  	{foreach from=$subcategories item=subcategory}
  	
  		
          	
        
  		{$subcategory.name|truncate:25:'...'|escape:'html':'UTF-8'}
  	
	{/foreach}

Explanation: once more, we are using the link class’s method to get the correct url pointing to the subcategory; then, we simply add an img tag, pointing directly to the category images folder, as each of them has an image named with the corresponding ID. Careful though! We have no way to check if the category has an image or not, and since the default method this theme uses is broken (heh.), you might as well get away without images.
At this point you should have something like this, depending on your images’ size:

It needs some styling, so let’s see what we can do with css!

Styling subcategories in PrestaShop 1.7

Open up theme.css, located in themes\classic\assets\css. At the very end, let’s append our css code:

.subcategory-heading {
  font-weight: bold;
}
#subcategories ul li {
  float: left;
  width: 25%;
  text-align: center;
}
#subcategories ul li img {
  margin-bottom: 10px;
}

I preferred staying on a simple styling here, and of course you will need to adapt the width depending on your category image size. Also, you might want to add media queries to make sure it displays well at smaller resolutions.
Save and refresh, we are done!

The post Adding subcategories to the category page in PrestaShop 1.7 appeared first on NemoPS.

Taking back the Add To Cart button in the Product list (Prestashop 1.7)

Nemo — Thu, 15 Dec 2016 08:20:33 +0000

If you started using PrestaShop 1.7 (brave!) and you miss the Add to Cart button in the product list, let’s see how to take it back with 4 lines of code!

Subscribe Post Scriptum's Youtube Channel

The post Taking back the Add To Cart button in the Product list (Prestashop 1.7) appeared first on NemoPS.

PrestaShop 1.7 is out, here is why it is a failure

Nemo — Wed, 09 Nov 2016 11:27:51 +0000

Last monday PrestaShop 1.7 has been released. Let’s see why it is a huge step backwards, driving the company dangerously downhill.

Following my previous post on why PrestaShop 1.7 will be a catastrophe, I thought it was high time to update my thoughts on it, given its official release. Have they changed? No. Here is why.

Slow slow slow

PrestaShop 1.7 is clearly slower than its predecessor. The installation itself (on localhost) took me over 10 minutes because of the page load, and kept hanging on the database connection settings. The new architecture is heavier, meaning it will need a better machine to run the same shop with the same performance. And this, for a merchant, means a bigger investment.

Ugly Design

PrestaShop has never shined for its template, but 1.6’s one was above the average level of a generic, free E-Commerce Platform. Whoever designed the “Classic” theme for PrestaShop 1.7 mistook “essential” with “poor”. This new theme is not “clean”, but rather just empty.
It looks bad, it feels bad and it’s lacking things more than being simplified. It’s dominantly starking white, and let’s just forget about images missing in the category header.
It’s not possible to set images for the top menu, which in return looks barely more than the result of a simple tutorial on creating mega menus.
In the product page, room for the long description has been sacrificed in favor of… nothing?
If you write a little more than a couple of lines (as you normally would, adding extra descriptions and media for the item) you will find yourself with a completely useless half of the page.

Ugly Urls

Some wise guy thought using a single id for each product was not enough. Hence, products with attributes now have 2 IDs in the url, one for the product itself, another for the combination. A plethora of us developers (including me) have developed their own versions of pretty urls, but the core team evidently thinks it’s not something merchants would want in 2016. Of course.

No bug fixes

Have you visited the PrestaShop Forge recently? I did.
Have a look at the bug reports VS fixes metrics on 1.6:
Is it really necessary to release a new version, leaving all these things unsolved?
The Development Team Leader Julien Martin stated 1.7 is not a release about bug fixing. Indeed, but they are still there.

No new features

In the article about the 1.7 release on the PrestaShop Development blog, Xavier Borderie mentions “a number of major features”. Let’s see what they are, according to him:
Symfony 2, new Default Theme and Starter Theme, New Product Back office, reworked modules page, reworked main menu.
Should we dissect them for a second?
Symfony 2: given the fact it’s only been implemented in 2 pages of the back office, it’s not really implemented in all the shop. The front office still uses Smarty.
Themes: I already said enough about the classic one, while the Starter Theme is simply one without any css or js.
New Product Back Office: I give him a point there, it’s the only new feature.
Reworked modules page: More following below
Reworked main menu: They just shuffled items and put some together, so that you have to click more to reach a page you were previously able to see right away (try to reach the customer groups page )
Are these new features? No. Only one is.

Core features removed

Here follows a list of features to which we bid adieu (seems appropriate) with the advent of PrestaShop 1.7:

One Page Checkout (!)
Cart Dropdown (!)
Advanced Stock Management
Font Awesome
Theme Configurator
Live search in the modules section, you have to hit enter
Send to a friend
Ajax removed from order history

Advertisement, plenty of.

As merchant, what would you like to see when you first click on the modules list? I would expect a page where I can configure modules. Things work differently at PrestaShop’s HQ. Apparently, what they like to see when they are configuring their shop is Advertisement. The first page we are presented with, as soon as we click on “modules”, is a nice list of “modules and services selected for you”. Nice.

Still no documentation

During the 1.7 installation process, you are embarrassingly given a link to the 1.6 documentation. Why is PrestaShop still lacking a decent official resource where to look for in case of issues?
Why is there still no sign of a real developer guide? I am guessing nobody really knows the code base.
We are given no indication at all, if any hint on the development blog. The code is not only not documented, it’s not even commented. Developers and users are just left on their own, trying to figure out the ins and outs of each feature, if it ever makes sense.
EDIT: It seems there is a work-in-progress documentation, as Krystian Podemski pointed out in the comments: http://developers.prestashop.com/ although it seems a bit confused to me.

Messed up code

As previously stated, 1.7 comes with a mixed architecture between the old code and Symfony 2. Some pages in the back office use Symfony, some modules use namespaces, the front office theme still uses Smarty, but differently. Overrides are formally deprecated but still available, because there is no valid alternative. Honestly, what should a developer do? Update modules? How, and why, when the core team doesn’t have a clear idea of the next steps, either?

The Puffin won’t save the day

The sad truth, PrestaShop, is that having a mascot won’t save the day. Updating visuals, making pretty commercials, full of dreams and promises, and then coming up with a software that’s a huge step backwards is not the way to go.
I solidarize with John James, who wrote an article on Medium.com, pointing out the faults of the company’s recent decisions. The new CEO, despite making things look prettier, didn’t bring anything good to PrestaShop, and is actually driving it downhill, through a path that will systematically push away every new potential user.
Using the software as bait to make money, by reducing its features, selling people what was previously given for free, is not on the path to popularity. Nor it will bring any growth, and Google Trends clearly show that the interest in PrestaShop is slowly, but constantly decaying.
PrestaShop is sinking, and it will drown unless they change their mentality for good.
We, developers, merchants, who survived and made a living thanks to it so far, can only hope for the good to happen. In the meantime, we will keep supporting 1.6, and, why not, continue to develop and fix bugs, even if just on our own, at least paying attention to our user base.

The post PrestaShop 1.7 is out, here is why it is a failure appeared first on NemoPS.

Prestashop 1.7 beta preview

Nemo — Wed, 08 Jun 2016 12:33:01 +0000

Prestashop 1.7 beta came out last week, let’s see how it has improved since the early alpha version we saw already

Watch the Screencast

Subscribe Post Scriptum's Youtube Channel

Additional Resources

Download Prestashop 1.7 Beta

The post Prestashop 1.7 beta preview appeared first on NemoPS.

PrestaShop 1.7 Pre-Beta video Preview

Nemo — Wed, 24 Feb 2016 09:31:14 +0000

In this first video on PrestaShop 1.7, we will see what’s the current state of development, exploring the front office and the product and modules catalog in the back office.

Watch the screencast

Subscribe Post Scriptum's Youtube Channel

More about PrestaShop 1.7

The post PrestaShop 1.7 Pre-Beta video Preview appeared first on NemoPS.