Use hooks to design your own modules that amplify functionality.
Instead of tampering with the original themes, duplicate them and apply your edits there.
For augmenting or altering functionalities, introduce it as a distinct module. When designing a module, hooks let you tweak core files indirectly. This method boasts benefits like:
For new hooks in upcoming Venddor IO versions, you can submit a request. However, please acquaint yourself with our hook creation standards.
If your goal is to modify the store's visual appeal, steer clear from the default theme. Instead, generate a standalone theme by duplicating your currently active one via the Administration panel:
From Venddor IO, a duplicated theme essentially contains the manifest.json file, default style, and logos. Every other piece of data is drawn from the parent theme, as indicated in manifest.json.
For customising, just transfer the pertinent files from the parent theme to the duplicated one, and initiate edits there.
Venddor IO saves CSS and TPL files of installed modules in the design/themes directory. Usually, when you uninstall a module, Venddor IO removes these files. If you reinstall, the system fetches files from var/themes_repository.
But in Development Mode, Venddor IO won't delete module files in design/themes upon uninstallation. However, if var/themes_repository holds any module .css or .tpl files, they'll replace the design/themes files upon module reinstallation.
For a clear view of error messages, modify PHP or server settings using:
error_reporting(E_ALL);
ini_set('display_errors', 'on');
ini_set('display_startup_errors', true);