Skip to main content

Posts

Showing posts from March, 2018

magento 1.9 to magento 2.X migration process using migration tool

According to the official Magento documentation, migration to the Magento 2 consists of four different stages: Theme Migration Extension Migration Customizations Data Migration Theme Migration Magento 2 introduces new methodologies and technologies for delivering enhanced shopping and store experience to the merchants and users. Developers can take advantages of new ways of creating awesome Magento 2 themes or modify the current ones to make them compatible with the Magento 2 standards. You should keep in mind that you cannot directly migrate your Magento 1 theme to Magento 2. You have to create a new theme for Magento 2 and make it responsive for the best user experience.  If you wish to avoid all this hassle, buy and install a Magento 2 theme from the Magento Marketplace or from other reputed sources. Extension Migration Extensions are essential components that provide new features and extend the functionalities of your Magento store. The next step in Magento mig

Grand Total not updated when discount code is applied

Please follow the below steps might be useful. Path:-  app/code/core/Mage/Sales/Model/Config/Ordered.php Comment this code::: /**      * Aggregate before/after information from all items and sort totals based on this data      *      * @return array      */     protected function _getSortedCollectorCodes() {         if (Mage::app()->useCache('config')) {             $cachedData = Mage::app()->loadCache($this->_collectorsCacheKey);             if ($cachedData) {                 return unserialize($cachedData);             }         }         $configArray = $this->_modelsConfig;         // invoke simple sorting if the first element contains the "sort_order" key         reset($configArray);         $element = current($configArray);         if (isset($element['sort_order'])) {             uasort($configArray, array($this, '_compareSortOrder'));         } else {             foreach ($configArray as $code => $data)

Magento array to string conversion bug

When i run my Magento 1.9 CE website on new php version(7.0.4) it start giving me error Array to string conversion in /var/www/bigliving.local/public_html/app/code/core/Mage/Core/Model/Layout.php on line 555 It happens because in PHP 7 you need to clarify that you are going to call the $callback variable as a method (function). So, the original line of the code looks like the following (file app/code/core/Mage/Core/Model/Layout.php): $out .= $this->getBlock($callback[0])->$callback[1](); In order to make it work on the latest PHP version we need to replace this piece of code by this one: $out .= $this->getBlock($callback[0])->{$callback[1]}(); Refer  this blog  for further information.  

Magento cron.php Does Nothing After it Runs

All cron jobs were scheduled but not executed. I found the solution in the forums  First Solution:::: Modifying core files is not a recommended practice at all. Luckily this solution is without editing we can solve , but first let me explain what this line is doing: The three lines before try to figure out if PHP is allowed to execute shell commands and set  $isShellDisabled = true if not. If it is false, cron.php will start two cron.sh processes in the background cron.sh /path/to/cron.php -mdefault cron.sh /path/to/cron.php -malways cron.sh in turn, runs cron.php (with the same arguments) if it doesn't find a running cron.php process. At least in theory, apparently checking for a running process does not work if the process has been spawned from cron.php as described above. Now, if $isShellDisabled is true, this is not possible and cron.php will run in both modes ("default" and "always") one after another. Solution You can leave out the firs