Required Apps |
Website (website)
|
Lines of code | 627 |
Technical Name |
web_website |
License | LGPL-3 |
Website | https://itpp.dev |
Also available in version | v 12.0 v 10.0 v 11.0 |
Multi-Brand Backend
Technical module to switch Websites in Backend similarly to Company Switcher
Version: v13.0.4.0.2
Tested and maintained by
IT Projects Labs
Assitance: help@itpp.dev
Let our expertise work for you!
(Doors and windows below are clickable)
/itpp-labs-1100.jpg)
/itpp-labs-930.jpg)
/itpp-labs-690.jpg)
Multi-Brand Backend
Installation
- Install this module in a usual way
- As this is a technical module, consider to install other modules that use this one, for example ir_config_parameter_multi_company
Configuration
Activate Multi Websites for Backend:
- Activate Developer mode
- Navigate to [[ Settings ]] >> Users >> Users and set [x] Multi Websites for Backend for selected users
Usage
Website Switcher
Once you activated Multi Websites for Backend, will see Website Switcher in top right-hand corner.
Company Properties
Via menu [[ Settings ]] >> Technical >> Parameters >> Company Properties (available in Developer mode) you can find exact values for Website-dependent fields. The menu shows normal Company-dependent fields too. To filter them out use new filter Website-dependent.
How it works
For a given record field and context (Company, Website), priority of the properties to be used as field's value is as following:
- Website and Resource are matched
- Website is matched, Resource is empty
- Company and Resource are matched, Website is empty
- Company is matched, Resource and Website are empty
- Company, Resource and Website are empty (i.e. only Field is matched)
Note, that when Company and Website are both set, Website's Company must be equal to Company or Empty. Otherwise such records are ignored.
On computing in non-website specific context it works as without the module, i.e.:
- Company and Resource are matched
- Company is matched, Resource is empty
- Company and Resource are empty (i.e. only Field is matched)
Please log in to comment on this module