Configuring Multiple Sites in One Plus2 Database
Problem
Operators running several sites in one Plus2 database need to keep each site's products, resources and booking sheets separate where needed, so a change at one site doesn't break another.
Resolution
Separate sites with site groups and prefixes
- Separate sites using site groups, consistent site-code prefixes, and site-specific products, subscriptions, activities, classes, resources and booking sheets where needed.
Decide whether each product is shared or site-specific
Use one shared product when… Use site-specific products when… Price, rules, tax, availability and description are identical everywhere A site may need to change it independently A future change should apply to every site Availability differs by site A resource may go offline at one site only Reporting and administration need clear site ownership - Separate site-specific products when a local change mustn't affect other sites. Site-specific records take longer to build but stop one site's change breaking another's.
Check four things before saving any item
- Check the current site indicator. Plus2 starts on Head Office, which has no booking sheets, so confirm the active site before creating or changing anything.
- Apply the correct site group.
- Check the site prefix in the ID.
- Decide whether it should be current-site-only or all sites.
Notes
- Test changes in the test database before applying them to live, and at every affected site.
- How to switch the current site is in Working Safely in Plus2 and Choosing the Current Site.
- Related: Naming Conventions for Plus2 IDs and Descriptions; Plus2 Resource Build QA and Go-Live Handover.