TopicMagento for Developers: Part 1
By: Allan Storm via devdocs.magento.com
What is Magento? It's the most powerful online eCommerce platform in the universe and is changing the face of eCommerce w88 live forever.
Of course, you already know that. What you may not realize is Magento's also an object-oriented PHP Framework that can be used to develop modern, dynamic web applications that tap into Magento's powerful eCommerce features.
This is the first in a series of articles in which we're going to go on a whirlwind tour of Magento's programming framework features. Don't worry if you don't follow everything immediately. As you study the system more everything in this article will start to make sense, and you'll soon be the envy of your colleagues stuck working with more primitive PHP systems.
Code Organized in Modules
Magento organizes its code into individual Modules. In a typical PHP Model-View-Controller (MVC) application, all the Controllers will be in one folder, all the Models in another, customer service m88. In Magento, files are grouped together based on functionality, which are called modules in Magento online baccarat Malaysia .
For example, you'll find Controllers, Models, Helpers, Blocks, etc. related to Magento's checkout functionality in
You'll find Controllers, Models, Helpers, Blocks, etc. related to Magento's Google Checkout functionality in
When you want to customize or extend Magento, rather than editing core files directly, or even placing your new Controllers, Models, Helpers, Blocks, etc. next to Magento code, you'll create your own Modules in
Package (also often referred to as a Namespace) is a unique name that identifies your company or organization. The intent is that each member of the world-wide Magento community will use their own Package name when creating modules in order to avoid colliding with another user's code.
When you create a new Module, you need to tell Magento about it. This is done by adding an XML file to the folder:
There are two kinds of files in this folder, the first enables an individual Module, and is named in the form: Packagename_Modulename.xml
The second is a file that will enable multiple Modules from a Package/Namespace, and is named in the form: Packagename_All.xml. Note it is only used by the core team with the file Mage_All.xml. It is not recommended to activate several modules in a single file, as this breaks the modularity of your modules.[url=https://w88you.com/]w88[\url]