Directory Structure for Modules in Venddor IO

For every module in Venddor IO, a specific directory structure is mandatory to ensure efficient functioning. Here's a comprehensive guide on how to organize your module's directories:

Primary Directory Structure

• Primary Directory: Every module should have its dedicated directory: app/addons/<module_name>. This directory will house the fundamental files and sub-directories crucial for the module's operation.
• addon.xml: This file encapsulates the primary metadata required for the module's installation and removal.
• func.php: This houses the functions which the module controllers employ.
• init.php: The primary objective of this file is to register a list of hooks that the module will utilize.
• config.php: This file contains the module's configuration data.

Essential Sub-directories

1. controllers: This directory accommodates the module's controller files and can also include pre- and post-controller files of Venddor IO's standard controllers.
2. schemas: This directory contains files that enhance the standard schemas of the platform.

Template Directories for Modules

In Venddor IO, modules can also employ additional directories to store template files:

• var/themes_repository/responsive/templates/addons/<module_name>: This path is intended for templates that are displayed in the user interface.
• design/backend/templates/addons/<module_name>: Templates specifically crafted for the administration panel are stored here.
• var/themes_repository/responsive/mail/templates/addons/<module_name>: This directory holds the email template files associated with the module.

Developer Flexibility

Developers have the liberty to create more subdirectories and files in this directory based on their unique requirements. However, it's crucial to maintain the naming and structural conventions parallel to the main Venddor IO application, adhering to the encryption standards.