Views in QloApps

To generate the views of QloApps, we are using the Smarty template engine: https://www.smarty.net/ (opens new window).

Theme views

The views are stored as .tpl files.

• Front office: These files belong to the allowed theme stored in the folder /themes/. For example, for the default theme, /themes/hotel-reservation-theme/product.tpl.
• Back office: These files belong to the allowed theme stored in folder /admin/themes/. For example, for the default theme, /admin/themes/default/template/controllers/products/information.tpl.

Module views

For adopting parts of the template, modules may incorporate their own templates:

• The front office: /modules/backwire/views/templates/front/payment_execution.tpl
• The back office: /modules/blocklayered/views/templates/admin/view.tpl

The view files that are connected to a specific hook are stored in a third template folder called /hook/.

Best practices

Generally, a view name is the same as the code name that uses it. For example, ProductController uses product.tpl.

Overriding

Because no inheritance exists, there is no way to overrule a view. To change a view, you must rewrite the template file in the same path and place it in your theme/module's folder.

You can use the QloApps/override/folder for views tied to a helper.

For example, if you want to modify the way front office order template file : admin/themes/default/template/controllers/orders/helpers/view/view.tpl

• you must copy the template file and its path to the override folder : /override/controllers/admin/template/orders/helpers/view/view.tpl
• then edit the template as per your requirements.

Do not forget to delete the /cache/class_index.php file when adding an override file manually, so that QloApps can take your changes into account.