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 1 extension converted in to magento 2 process

Simple Install =================================== Download as a zip below link. unzip and upload it to your public_html or other rootdoc directory. https://github.com/magento/code-migration. login to your server via shell switch to the code-migration-develop directory by running following command   cd code-migration-develop Run command following command in root directory of this toolkit composer instal Before running the migration, the following directories need to be prepared: ===================================== * `<src>` - Directory that contains custom Magento 1.x code that is intended to be migrated. The code must follow the Magento 1.x directory structure.   Magento1.x core files must not be included. * `<dst>` - Empty directory for the toolkit to put the generated Magento 2 code to * `<m1>` - Directory that contains: * Vanilla Magento 1.x codebase, and * Custom Magento 1.x code same as...

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 Debug HEADERS ALREADY SENT error

When you  receiving the following error in  system.log file: app\code\core\Mage\Core\Controller\Response\Http.php:44  [1] \www.pawan.com\lib\Zend\Controller\Response\Abstract.php:727  [2]  \www.pawan.com\app\code\core\Mage\Core\Controller\Response\Http.php:75  [3]  \www.pawan.com\app\code\core\Mage\Core\Controller\Varien\Front.php:188  [4]  \www.pawan.com\app\code\core\Mage\Core\Model\App.php:304  [5]  \www.pawan.com\app\Mage.php:596  [6]  \www.pawan.com\index.php:81 if you have no idea what file is causing this. Here is the steps to debug. That error is thrown from Mage_Core_Controller_Response_Http -> sendHeaders(). This function calls the super class function that actually does the check to see whether or not headers have already been sent, Zend_Controller_Response_Abstract -> canSendHeaders(). The Zend_Controller_Response_Abstract class handles, among other things, sending response header...