Download the appropriate Magento PHP 7.2 compatibility patch from https://magento.com/tech-resources/download and copy it to the root directory of your Magento installation. You may have noticed that the patch filename differs slightly from the usual security patch names. There is no…
Magento 1 and PHP 5.6 support
Support for PHP 5.6 ends at the end of 2018! Many hosting providers may therefore stop offering this PHP version. Act early and make your Magento 1 store ready for PHP 7. In many cases, the switch is manageable in…
Magento 1 and PHP 7
The benefits of PHP 7 are clear: it is faster and more secure than older versions, and offers developers new ways to write code and build features. Sooner or later, any Magento 1 store owner will reasonably ask whether the…
Cache Warmer for Magento 1 and Magento 2
What is a Magento cache warmer, and how can it help your Magento 1 or Magento 2 store run smoothly? In simple terms, a cache warmer visits all your store URLs in the background, for example once a day at…
Reindexing URL rewrites (Magento 2)
Magento 2 URL rewrites are not updated simply by rebuilding the indexes. If you want to rebuild them from the command line, I recommend using https://github.com/olegkoval/magento2-regenerate_url_rewrites. This extension lets you regenerate all Magento 2 URL rewrites from the shell. Afterwards,…
Creating a database backup from the command line (Magento 2)
To back up your Magento 2 database from the command line, run this command from the root directory of your Magento 2 installation:
|
1 |
php bin/magento setup:backup --db |
SEO tip: URLs for translated content in Magento 1 and 2
If your Magento store supports several languages, you should also give translated content, such as product pages, distinct URLs for each language. If your German product page is called www.ihreseite.de/ihrprodukt.htm, the English product page should, for example, use www.ihreseite.de/yourproduct.htm lauten.
Checkout progress no longer works (Magento 1)
If the checkout progress indicator no longer appears in Magento, the problem is almost certainly related to your theme. Open the theme’s checkout.xml file and add the following code:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 |
<checkout_onepage_progress_billing> <!-- Mage_Checkout --> <remove name="right"/> <remove name="left"/> <block type="checkout/onepage_progress" name="root" output="toHtml" template="checkout/onepage/progress/billing.phtml"> <action method="setInfoTemplate"><method></method><template></template></action> </block> </checkout_onepage_progress_billing> <checkout_onepage_progress_shipping> <!-- Mage_Checkout --> <remove name="right"/> <remove name="left"/> <block type="checkout/onepage_progress" name="root" output="toHtml" template="checkout/onepage/progress/shipping.phtml"> <action method="setInfoTemplate"><method></method><template></template></action> </block> </checkout_onepage_progress_shipping> <checkout_onepage_progress_shipping_method> <!-- Mage_Checkout --> <remove name="right"/> <remove name="left"/> <block type="checkout/onepage_progress" name="root" output="toHtml" template="checkout/onepage/progress/shipping_method.phtml"> <action method="setInfoTemplate"><method></method><template></template></action> </block> </checkout_onepage_progress_shipping_method> <checkout_onepage_progress_payment> <!-- Mage_Checkout --> <remove name="right"/> <remove name="left"/> <block type="checkout/onepage_progress" name="root" output="toHtml" template="checkout/onepage/progress/payment.phtml"> <block type="checkout/onepage_payment_info" name="payment_info"> <action method="setInfoTemplate"><method></method><template></template></action> </block> <action method="setInfoTemplate"><method></method><template></template></action> </block> </checkout_onepage_progress_payment> |