Bitrix Framework

• Database account is created in the Sites administrative menu and includes the following main parameters:
  • Identifier – a set of symbols identifying the site;
  • Domain name – one or more domain names of the site;
  • Site folder – a path to the catalog where the public part of the site will be stored;
  • Language of the site;
  • Date and time format;
  • URL - a default protocol and domain name (for example: http://www.site.com);
  • DocumentRoot - if multi-siting is organized on different domains, this parameter must contain a path through the server file system to the site root;
  • Template connection conditions – each site may have one or more templates for reflecting scripts of its public part, each of such templates may be connected according to a certain condition;
• Public part – is a set of scripts (pages) located in the “site folder” and belonging to this site;
• Settings – each module may have a number of settings associated with the site; for example the settings of the Information Blocks module represent the binding of an information block to a certain site, and the settings of the Helpdesk module determine the binding of a status, category, etc. to the site.

• a set of files in the directory /bitrix/templates/template_ID/, where template_ID is an ID field in the form of a site template editing. The structure of this directory is as follows:
  • /components/ - directory with components belonging to a certain module;
  • /lang/ - language files belonging both to this template in general and to separate components;
  • /images/ - a directory with images used in this template;
  • /page_templates/ - a directory with page templates and their description stored in the file .content.php;
  • /include_areas/ - a directory with content files of the areas to be included;
  • header.php - is a prologue of this template;
  • footer.php - is an epilogue of this template;
  • styles.css - CSS styles applied on the site pages when this template is used;
  • template_styles.css - CSS styles used in the template itself;
  • .menu type.menu_template.php - a template for displaying menu of a relevant type;
  • chain_template.php - a default template for display of navigational chain;
  • and also a number of other auxiliary random files included in this template.

• master file connects using the function CMain::IncludeFile which represents a PHP script implementing the logic of component;
• language files - are used in component to display its result in different languages;
• description - is a PHP code used by visual editor to manage component and its parameters.

• Download product updates;
• Upload new modules and updates for existing modules to extend their functionality;
• Upload language files and install new languages;
• Register licenses for additional sites.

The system is updated in several steps:

• The update system automatically requests a license key of the product;
• Next, a check of the available updates is performed;
• Then, a user is offered to select updates for downloading;
• After that, selected updates are downloaded.

• /bitrix/templates/site_template_ID/;
• /bitrix/templates/.default/;
• /bitrix/modules/module_ID/install/templates/

• Identifier;
• Name;
• Date format;
• Time format;
• Encoding.

• /bitrix/templates/site_template_ID/page_templates/
• /bitrix/templates/.default/page_templates/

Generally, this term means the top left part of a page.

For the public part the prologue of the relevant site template is stored in the file /bitrix/templates/site template ID/header.php.

For the administrative part the prologue is stored in the file /bitrix/modules/main/interface/prolog_admin.php.

In its turn, the prologue may be divided into a service and a visual part. In the service part, all the necessary classes are connected, connection with the base is established, and a number of service instances of objects such as $USER, $APPLICATION, etc. are created. In the visual part, top left part of the page is displayed.

If an undivided prologue must be connected in the public part, we use the following code:

require($_SERVER["DOCUMENT_ROOT"]."/bitrix/header.php");

If due to any reasons we have to divide the prologue into a service (prolog_before.php) and a visual (prolog_after.php) part, we use the following codes:

require($_SERVER["DOCUMENT_ROOT"].
"/bitrix/modules/main/include/prolog_before.php");
...
require($_SERVER["DOCUMENT_ROOT"].
"/bitrix/modules/main/include/prolog_after.php");

Generally, this term means the bottom right part of a page.

For the public part, the epilogue of the relevant site template is stored in the file /bitrix/templates/site template ID/footer.php.

For the administrative part, the epilogue is stored in the file /bitrix/modules/main/interface/epilog_admin.php.

In its turn, the epilogue may be divided into a service and a visual part. Some actions like sending mail messages, execution of OnAfterEpilog event handlers, etc. are performed in the service part. In the visual part, the bottom right part of the page is displayed.

If an undivided epilogue must be connected in the public part, we use the following code:

require($_SERVER["DOCUMENT_ROOT"]."/bitrix/footer.php");

If due to any reasons we have to divide the epilogue into a visual (epilog_before.php) and a service (epilog_after.php) part, we use the following codes:

require($_SERVER["DOCUMENT_ROOT"].
"/bitrix/modules/main/include/epilog_before.php");
...
require($_SERVER["DOCUMENT_ROOT"].
"/bitrix/modules/main/include/epilog_after.php");

• This page does not belong to any site;
• At the same time it belongs to a module;
• It has a strictly determined administrative interface;
• All localization parameters of this page depend on a selected current language;
• Additional verification of rights established in the settings of a relevant module is used on this page.

• This page belongs to a site;
• It has an interface of a current site template;
• All localization parameters of this page depend on the current site.

• Apache - in the file httpd.conf, parameter DirectoryIndex;
• IIS - in site properties, tab Documents > Enable default content page;

• Login;
• Password;
• E-Mail,

and also a number of additional fields containing a user’s personal information, information about a user’s work, and administrative notes.

Registration data (login and password) indicated by the user during registration or obtained by the user automatically (e.g., after importing) will be used for authorization in the system. Following registration, the user is allocated to a specific group and receives the right to access portal resources in accordance with the rights granted to such group.

• Administrative section;
• Error messages;
• Visual components;
• Relevant areas in the portal template;
• etc.

• 4 - read;
• 2 - write;
• 1 - execute.

The sum of these numbers gives a final set of rights; e.g. 6 is read and write but without execute; 7 – all rights; 5 – read and execute.

Thus, e.g., the right 764 will mean: 7 – all rights for the file owner, 6 – read and write for the users’ group to which the file owner belongs, and 4 – read for all other users.

In PHP, all rights are indicated as octal numbers, and they must be given indicating prefix 0 without fail. Example: 0755.

• for Apache – in the file httpd.conf, parameter DocumentRoot;
• for IIS – in the site properties; tab Home Directory > Local Path.