Dashboard RSS Feed

[...] set of "container" and "block" elements Example of declaration in layout: View Online [...]

[...] used in router's class implementation (for example, Mage_Core_Controller_Varien_Router_Base). View Online [...]

[...] revision 1 and revision 2: ... View Changes Online View All Revisions | Revert To Version 1 View Online [...]

[...] ', but the correct capitalization would be 'Mage_CatalogInventory_Model_Stock'. View Online [...]

[...] . Where possible these standards and requirements are enforced using [Automated Static Code Analysis Tests]. Standards and requirements which cannot be automatically validated must be applied [...]

[...] with Magento 2.x real table names. The algorithm in details: Include bootstrap of the static code analysis tests (dev/tests/static/framework/bootstrap.php). Collect all PHP files in the system, [...]

[...] , including layout updates. The algorithm in details: ... # Include bootstrap of the static code analysis tests ({{dev/tests/static/framework/bootstrap.php}}) # Collect all PHP and XML-files in the [...]

[...] Page edited by Aleksandra Marchenko Changes between revision 8 and revision 9: ... [Container|Containers and Blocks] is a [...]

[...] Page edited by Aleksandra Marchenko Changes between revision 6 and revision 7: ... {warning:title=Warning} This page is incomplete. [...]

[...] Page edited by Aleksandra Marchenko Changes between revision 11 and revision 12: ... {note} The page is not complete {note} { [...]

[...] Page edited by Aleksandra Marchenko Changes between revision 1 and revision 2: {warning} The page is not complete {warning} { [...]

[...] merged after materialization. The [page layout|Page Layouts] file identifies the JavaScript and CSS files to be merged; the process of merging the two types of files is nearly identical. {column} { [...]

[...] merged after materialization. The [page layout|Page Layout] file identifies the JavaScript and CSS files to be merged; the process of merging the two types of files is nearly identical. {column} { [...]

[...] of static resources that comprise the graphical user interface, including: * Style sheets: CSS files used to control visual styling of the website * Javascript: JS files containing theme-specific [...]

[...] (../blue/img.gif) - for the frontend/default/default/blue Because of these potential variations, CSS files must always be duplicated. View Online [...]

[...] from {{phpunit.xml}} (or {{phpunit.xml.dist}}), serve as the entry point to launch the Magento application and initiate proper environment shutdown. The bootstrap algorithm will: # Check whether the [...]

[...] of the Magento view layer. h3. Page Page is a document (generally a web-page) generated by Magento application and intended to be displayed to end-user. h3. Page Type Page types are distinguished by [...]

[...] } {column:width=70%} The article describes the process of installing/upgrading modules of Magento application. Installation and upgrade procedures for Magento modules are similar. {column} {column} { [...]

[...] of the Magento view layer. Page Page is a document (generally a web-page) generated by Magento application and intended to be displayed to end-user. Page Type Page types are distinguished by [...]

[...] 'admin_role'){code} | {code}getTableName('admin_role'){code} | In Magento 2, configuration files do not contain table definitions in {{/config/global/models/*/entities}}. All existing [...]

[...] made during installation. At the beginning of code execution the system collects these configuration files, loads and merges them with one another to create the configuration file that will be used [...]

[...] is to specify its name directly. Was in Magento 1.x Became in Magento 2.x In Magento 2, configuration files do not contain table definitions in /config/global/models/*/entities. All existing table [...]

[...] The output prepared by the Block classes is arranged and rendered by a set of templates and configuration files, which determine positioning and properties of the Blocks output. The {{view}} folder [...]

[...] Comment added by Aleksandra Marchenko JIRA: JIRA project does not exist or you do not have permission to view it. View Online [...]

[...] Comment edited by Aleksandra Marchenko JIRA: JIRA project does not exist or you do not have permission to view it. View Online [...]

[...] Comment edited by Aleksandra Marchenko JIRA: Unable to determine if sort should be enabled. JIRA: Unable to determine if sort should [...]

[...] Comment added by Aleksandra Marchenko JIRA: JIRA project does not exist or you do not have permission to view it. View Online [...]

[...] revision 8 and revision 9: ... To exactly control the look and feel of each store in your Magento installation, Magento allows you to create themes. Related themes are grouped together in design [...]

[...] application files and upload them to your web server * Create a MySQL database for your Magento installation * If you're using a Linux or Unix operating system, ensure that the following directories [...]

[...] } h3. Design Packages A Design Package is a collection of related Themes. By default, each Magento installation includes a Design Package specific to the edition of Magento installed: || Edition || [...]

[...] revision 11 and revision 12: To exactly control the look and feel of each store in your Magento installation, Magento allows you to create themes and skins. Related themes are grouped together in [...]

[...] static view files and other view files is that they must be publicly accessible. Since the module folder is not publicly accessible, the static view files are automatically [materialized|Skin Files [...]

[...] that don't belong to a module. Therefore, it is required to locate each template in a module folder under a theme. Each template file should have module scope identifier ({{<Module_Name>:: [...]

[...] that don't belong to a module. Therefore, it is required to locate each template in a module folder under a theme. Each template file should have module scope identifier ( ::path/to/template. [...]