Magento security patch SUPEE-6788 released on the 27th of October 2015 fixes more than 10 security problems including remote execution and data leaks. It has been included in Magento 18.104.22.168. Unfortunately, at the same time as adding numerous fixes, it affects several extensions. So the best way to deal with these issues is to make a development copy of your site before installing the patch and install the patch there. You can find our more about it here. (more…)
When scrolling pages down, Mаgentо adds a line at the top of the page: (more…)
Data output to the browser
Data for output to the browser accumulates in the controller in the internal variable Mage_Core_Controller_Response_Http::_body, and is displayed by calling Mage_Core_Controller_Response_Http::appendBody(). In most cases, processing is carried out through the Layout object and is ended by calling $this->renderLayout(): (more…)
We suppose you continue following our Magento certification-dedicated posts in our blog. This time we will tell you about class naming conventions and their relationship with the autoloader.
Magento was developed based on the Zend Framework, so the rules of class naming in Magento were taken from the Zend Framework (read more here).
Magento standardizes class names depending on their location in the file system. Such standardization enables automatic class loading (autoloader) instead of using require_once and include_once functions. Rather than the directory separator (‘/’ – invalid character for class names), developers use the underscore character (‘_’).