![\"Prestashop](\"http:\/\/www.confianzit.com\/cit-blog\/wp-content\/uploads\/2014\/07\/Prestashop-Module-Development.jpg\")
<\/a><\/p>\nThis article explains how to create a module for prestashop<\/strong><\/a>. Let\u2019s create a simple module and will name it \u2018 My module<\/strong> \u2019. This folder must contain the main file, a PHP file of the same name as the folder, which will handle most of the processing: mymodule.php <?php<\/p>\n if (!defined(‘_PS_VERSION_’))<\/p>\n exit;<\/p>\n <\/p>\n This checks for the existence of an always-existing prestashop<\/a> constant (its version number), and if it does not exist, it stops the module from loading. The sole purpose of this is to prevent malicious visitors to load this file directly.<\/p>\n The main file (mymodule.php) must contain the module’s main class, and that class must bear the same name as the module and its folder, in CamelCase and that class must extend the Module class, in order to inherit all its methods and attributes. (It can just as well extend any class derived from Module, for specific needs: PaymentModule, ModuleGridEngine, ModuleGraph, etc.)<\/p>\n At this stage, the module can already be seen in the “Modules” page in the back-office (in the “Other modules” section) \u2013 albeit with no real name nor thumbnail.<\/p>\n Now, let’s fill the class code block with the essential constructor lines. Our mymodule.php file will look like this now. The use of each attribute in the constructor is explained below. <?php<\/p>\n if (!defined(‘_PS_VERSION_’))<\/p>\n exit;<\/p>\n class MyModule extends Module<\/p>\n {<\/p>\n public function __construct()<\/p>\n {<\/p>\n $this->name = ‘mymodule’;<\/p>\n $this->tab = ‘front_office_features’;<\/p>\n $this->version = ‘1.0’;<\/p>\n $this->author = ‘Firstname Lastname’;<\/p>\n $this->need_instance = 0;<\/p>\n $this->ps_versions_compliancy = array(‘min’ => ‘1.5’, ‘max’ => ‘1.6’);<\/p>\n parent::__construct();<\/p>\n $this->displayName = $this->l(‘My module’);<\/p>\n $this->description = $this->l(‘Description of my module.’);<\/p>\n $this->confirmUninstall = $this->l(‘Are you sure you want to uninstall?’);<\/p>\n if (!Configuration::get(‘MYMODULE_NAME’))<\/p>\n $this->warning = $this->l(‘No name provided’);<\/p>\n }<\/p>\n }<\/p>\n <\/p>\n $this->tab: The title for the section that shall contain this module in the back-office modules list.<\/p>\n $this->version: The version number for the module, displayed in the modules list.<\/p>\n $this->author: Name of author.<\/p>\n $this->need_instance: Indicates whether to load the module’s class when displaying the “Modules” page in the back-office. If set at 0, the module will not be loaded, and therefore will spend less resources to generate the “Modules” page. If your module needs to display a warning message in the “Modules” page, then you must set this attribute to 1.<\/p>\n $this->ps_versions_compliancy: Indicates which version of prestashop\u00a0this module is compatible with.<\/p>\n parent::__construct(): Call the constructor method from the parent PHP class. By default, this will trigger a lot of actions from PrestaShop. Calling the parent constructor method must be done after the creation of the $this->name variable and before any use of the $this->l() translation method.<\/p>\n $this->displayName: A name for the module, which will be displayed in the back-office’s modules list.<\/p>\n $this->description: A description for the module, which will be displayed in the back-office’s modules list.<\/p>\n $this->confirmUninstall: A message, asking the administrator if he really does want to uninstall the module.<\/p>\n $this->warning: Show any warning messages. The install() and uninstall() methods make it possible to control what happens when the store administrator installs or uninstalls the module. They must be included in the main class’ block of code (MyModule class) \u2013 at the same level as the constructor method.<\/p>\n The install() method basically does all the things when the module is installed. (For example, registering hooks, updating Configuration values, Adding new tables required for the module, etc.) public function install()<\/p>\n {<\/p>\n if (Shop::isFeatureActive()) {<\/p>\n Shop::setContext(Shop::CONTEXT_ALL);<\/p>\n }<\/p>\n if (!parent::install() ||<\/p>\n !Configuration::updateValue(‘CODE_BLOCK_VALUE’, ‘My code block value’)<\/p>\n ) {<\/p>\n return false;<\/p>\n }<\/p>\n return true;<\/p>\n }<\/p>\n <\/p>\n public function uninstall()<\/p>\n {<\/p>\n if (!parent::uninstall() ||<\/p>\n !Configuration::deleteByName(‘CODE_BLOCK_VALUE’)<\/p>\n ) {<\/p>\n return false;<\/p>\n }<\/p>\n return true;<\/p>\n }<\/p>\n <\/p>\n Now that all basics are in place, reload the back-office’s “Modules” pages, in the “Front-office features” section, you should find your module. Install it (or reset it if it is already installed).<\/p>\n During the module’s installation, PrestaShop automatically creates a small config.xml file in the module’s folder, which stores the configuration information. PrestaShop also adds a row to the ps_module SQL table during the module installation.<\/p>\n <\/p>\n We hope this article about\u00a0Prestashop Module Development<\/a> was helpful please post your thoughts and comments \u00a0below .<\/p>\n Confianz Global Inc. is a leading\u00a0<\/span>Odoo ERP Development Company in USA<\/a>. Get in touch with us for\u00a0<\/span>Odoo ERP Customization<\/a>\u00a0<\/span>&\u00a0<\/span>Implementation<\/a>. Give us a call today<\/a>!<\/p>\n <\/span><\/p>\n <\/p>\n [\/et_pb_text][\/et_pb_column][et_pb_column type=”2_5″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_code _builder_version=”4.21.0″ _module_preset=”default” animation_style=”bounce” animation_direction=”top” sticky_position=”top” sticky_offset_top=”20px” sticky_limit_bottom=”column” sticky_transition=”off” motion_trigger_start=”top” global_module=”2151″ locked=”off” global_colors_info=”{}”]<\/p>\n
First, create a folder for the module in the <HOME_DIRECTORY>\/modules folder and it should have the same name as the module, with no space, only alphanumerical characters, the hyphen and the underscore, all in lowercase:
(This will be our folder structure: <HOME_DIRECTORY>\/modules\/mymodule.)<\/p>\n
The main mymodule.php file must start with the following test:<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code>
$this->name: Serves as an internal identifier. The value must be the name of the module’s folder. Do not use special characters or spaces, and keep it lower-case<\/p>\n
The install() and uninstall() methods<\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code>
The uninstall() method basically does the inverse of install() method. (For example, removing Configuration values which was stored when the module was installed, removing tables, etc.)<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code><\/p>\n<\/code>
As you can see most of the methods make use of a new Configuration object. This is a PrestaShop-specific object, built to help manage the module settings. It stores these settings in the database without require to use SQL queries. Specifically, this object handles data from the ps_configuration database table.<\/p>\n<\/a><\/p>\n<\/a><\/p>\n