Skip to main content

5 worst Magento practices

I hope this article will help many to save their eCommerce problem and to optimize their code. Magento is a wonderful platform to kick start your e-commerce endeavors. But the worst part is its development flow.

I will introduce you the 5 worst Magento development practices followed by detailed example.

1. Collections – query results limitation


To improve code performance and scalability remember to apply limitation on the collection’s query results — it’s much better to do $collection->getSize() instead of $collection->count() or count($collection) because that ways, all of the items will be loaded from the database and than iterated.


2. SQL queries inside a loop


Bad practice is to load Magento models inside a loop. Running SQL query is very expensive operation and doing it in a loop tends to make it even worse. Instead of doing that we could use data collections to load models and then process it.  To be careful when working with collection to do not exceed memory.  Consider $productIds is array of product data.

Bad:
foreach ($productIds as $productId){
    $product = Mage::getModel('catalog/product')->load($productId);
    $this->Storeproducts($product); 
}
Good:
$collection = Mage:getModel('catalog/product')->addFieldsToFilter('entity_id',array('in' => $productIds); foreach ($collection as $product){
$this->Storeproducts($product); }

3. Models loading
We need to remember that each time of executing load() method, separate query’ll be executed on a database. Also loading multiple models separately, slows down our code. Models should be loaded only once with a single SQL query.
Bad:
$name = Mage::getModel('catalog/product')->load($productId)->getName();
$sku = Mage::getModel('catalog/product')->load($productId)->getSku();
Good:
$product = Mage::getModel('catalog/product')->load($productId);
$name = $product->getName();
$sku = $product->getSku();
We also don’t always need the whole model to be loaded — we can do it only when its necessary. In other cases, load only attributes which are needed.
$productId = Mage::getModel('catalog/product')->getIdBySku($sku);  

4. Counting array

PHP function count() is fast but when used in a loop this changes really severely. Calculating the size of an array on each iteration of a loop, if the array or collection contains a lot of items, will result in much longer execution time. Counting size should be done outside the loop not on each iteration.
Bad:
for ($i = 0; $i < count($array); $i++){
    echo $1;
}
Good:
$size = count($array);
for ($i = 0; $i < $size; $i++){
   echo $1;
}

5. Image Optimization


Product image – 250px / 250px and Thumbnail – 120px / 120px
If you want to serve different images for mobile site, always declare width and height for them. 
Don’t make the dimension larger and make sure that all your product images are of the same dimensions for height and width.

Comments

Popular posts from this blog

Magento 2 product collection Filtering multi-select attribute values

  If you have multi-select attribute of product like below If you want filter value for this option Use below syntax to get product data: ->addAttributeToFilter('store_model', array('finset' => $params['store_model'])) finset key is used for multiselect attribute filter. $objectManager = \Magento\Framework\App\ObjectManager::getInstance(); $products = $objectManager->get('Magento\Catalog\Model\Product')         ->getCollection()         ->addAttributeToSelect('*')         ->addAttributeToSelect('store_brand')         ->addAttributeToSelect('store_model')         ->addAttributeToSelect('store_year')         ->addAttributeToFilter('store_brand', array('finset' => $params['store_brand']))         ->addAttributeToFilter('store_model', array('finset' => $params['store_model']))         ->ad...

magento 2 best seller product display based on current category and subcategories

Magento 2 getting best seller based on category wise displaying i have done below for that to implement this functionality it is working fine for me. step 1 create block file in our module folder <?php namespace Pawan\Bestseller\Block; use Magento\Catalog\Api\CategoryRepositoryInterface; class Bestsellercategory extends \Magento\Catalog\Block\Product\ListProduct {     /**      * Product collection model      *      * @var Magento\Catalog\Model\Resource\Product\Collection      */     protected $_collection;     /**      * Product collection model      *      * @var Magento\Catalog\Model\Resource\Product\Collection      */     protected $_productCollection;     /**      * Image helper      *      * @var Magento\Catalog\Helper\Image     ...

Integrity constraint violation: 1052 Column 'created_at' in where clause is ambiguous

When trying to filter sales order grid with From and To dates it was redirecting to dashboard.after that again i tried to open sales order grind it is generating reports in reports file it showing. "Integrity constraint violation: 1052 Column 'created_at' in where clause is ambiguous" means it is finding a another created_at field. because when we adding or joining the other table then it has also a field named as created_at. So below is the  solution for this error. magento that created_at is of the main_table not of my custom table. Find the below code in the sales order grid.php file. $this->addColumn('created_at', array(            'header' => Mage::helper('sales')->__('Purchased On'),             'index' => 'created_at',             'type' => 'datetime',             'width' => '100px',         )); ...