-
What is Bitrix Framework?
-
Production Architecture
-
Production Architecture
-
Structure of files
-
Access Rights
-
A Site in Terms of Bitrix Framework
-
-
Processing Techniques
-
Core D7
-
Modules
-
Name Spaces
-
Core Parameter Setup
-
Exceptions
-
Events
-
Code Writing Rules
-
Applications and Context
-
Errors
-
ORM
-
API
-
Highloadblock
-
-
Design Integration
-
Using Access Rights
-
Site Design Template
-
Using message files for localization
-
Editable areas
-
Navigation tools
-
Advertisement
-
Managing Template Service Data
-
Editing Service Areas
-
Managing Page Encoding
-
Managing Document Header
-
Managing Metadata Values
-
CSS management
-
-
Setup of External Appearance of Additional Elements of the Site Design
-
-
Information Blocks
-
Working with Infoblocks Using Standard Means
-
Infoblocks 2.0
-
Action Plan in Case of Problems
-
Sorting
-
Work with Infoblocks through API
-
Examples
-
-
Components
-
Simple and composite components
-
Location of a Component in the System and Its Connection
-
Component Structure
-
Composite Component Structure
-
Component Description
-
Component Parameters
-
Component Templates
-
Support of Component Classes
-
result_modifier.php
-
component_epilog.php
-
Operation of a Composite Component in a SEF Mode
-
Frequent Errors
-
Component Caching
-
Working with Components
-
Template Customization
-
Component Customization
-
Creating Components
-
Additional Methods
-
Redefinition of Incoming Variables
-
User-Defined Templating Engines
-
Operation of a Composite Component in SEF Mode
-
Ways of Data Transmission among Components
-
A Simple Example of a Component Creation
-
Component Creation Example
-
TinyMCE Visual Editor Integration Component
-
Caching in own components
-
-
CUSTOM Parameter Type
-
More examples
-
Errors When Working with Components
-
-
-
Modules
-
Programming in Bitrix Framework
-
Golden Rules
-
The file init.php
-
UTF-8 or a National Encoding?
-
Working with Databases
-
Setup of SEF for URLs
-
Language Files
-
JS Library
-
Interface of the Control Panel Toolbar as Seen by a Developer
-
Some Theory
-
Performance
-
Security
-
Examples, tricks, and advice
-
Custom Fields
-
Gadgets
-
Project Testing
-
Project Quality Control
-
Debugging Web Applications
-
-
Push and Pull module
-
Version Control System
-
-
Multiple Sites
-
Introduction
-
Use of Multiple Site Version
-
How many sites can I create?
-
Language versions (mirrors)
-
Sharing visitors between sites
-
Configuring the multisite system
-
Working with the Data in a Multiple Site Configuration
-
Frequent Questions Arising When Working with a Multiple Site Configuration
-
-
Business Processes for Developer
-
Template of a Business Process
-
Business Process
-
Activities
-
Executing a business process activity using API
-
Arbitrary PHP Code in a Business Process
-
-
Additional Information and Examples
Multiple Site in One Domain
Lesson 220 out of 253
The main requirement for a multiple site in one domain is separation of sites by subcatalogs so that the file structure does not overlap. Each site must be located in a separate subcatalog inside the root catalog.
In this case, the creation of equivalent folders in the root catalog structure and the creation of folders for the second site inside the directory of the first site are possible. I.e., the following combinations are acceptable:
/www/s1/
- first site,-
/www/s2/
- second site.
/www/s1/
- first site,-
/www/s1/s2
– second site.
The system is delivered with a multiple site configuration in one domain. Additional settings in the file httpd.conf of Apache web server are not necessary, it is enough to just create the required folders and correctly complete fields in site settings.
Setup of Multiple Site in One Domain
In order to determine settings for a multiple site in one domain we have one web server Apache, which DocumentRoot is configured to the catalog /home/www/allsites/
.
The path to the site root in the server file system is set up in the web server settings, for example:
- For Apache - in the file httpd.conf, parameter DocumentRoot;
- For IIS - in the site properties, tab Home Directory > Local Path.
Install Bitrix Site Manager software into this catalog.
Each site in the first configuration option must be located in a separate subcatalog inside a unified catalog, e.g.:
/home/www/allsites/s1/
/home/www/allsites/s2/
The names of catalogs s1 and s2 can be different, e.g. shop and company, or en and de, accordingly. One of the sites can also be located in the root catalog (e.g., /home/www/allsites/
), and the second site in the subcatalog (e.g., /home/www/allsites/s2/
).
Website Configuration
Websites are configured in the Administrative part of the system (Control Panel > Settings > > System settings > Websites > Websites).
Let us set up parameters for site No. 1:
- Name: site1
- Domain: leave empty
- Site folder: /s1/
- Website name: Corporate Website of " Company Name"
- Server URL: www.site1.com/s1
- Path to the web server root folder of this site: leave empty
The parameter "Site folder" must contain the path from the root to the catalog where the public part of the site is located. "Path to the web server root folder of this site" is not used in this multisite configuration option and should be left empty for all websites.
Similarly, let us set up parameters for site No. 2:
- Name: site2
- Domain: leave empty
- Site folder: /s2/
- Website name: E-Store of "Company Name"
- Server URL: www.site1.com/s2
- Path to the web server root folder of this site: leave empty
Multiple site in one domain on IIS web server is implemented similarly to the procedure used for Apache server.