Bitrix24 Self-hosted administration

• are not part of any site managed by the system;
• are provided by a specific module;
• conform to the Control Panel user interface guidelines;
• display their content using the selected UI language;
• are always checked for permissions specified in the settings of their respective module.

• always belong to a specific site;
• have the UI of the applied site template;
• display content using the language currently selected for their site.

• a special account, or record in the database - This record is created by a user (administrator) in Control Panel using the Sites menu:
  • ID - a string of characters uniquely identifying the site;
  • domain name - a site can have multiple domain names assigned to it;
  • site folder - a physical folder in the file system containing the website files;
  • site language;
  • date and time format;
  • URL - a fully qualified address to access the site over the Internet. Includes a protocol and the domain name (for example, http://www.site.com);
  • DocumentRoot - in a multisite configuration existing on different domains, this parameter specifies the site root path in the server file system;
  • template activation conditions. Each site can have one or more templates to show the site content. If there are multiple templates, these conditions specify when a specific template should be applied;
• Public area, section - pages stored in the site folder;
• Settings - each of the system modules can have a number of site-specific parameters. For example, Information block module assigns an iblock to a specific site. The Helpdesk module can have site-specific statuses and categories.

• /components/ - contains components used by the system modules;
• /lang/ - localization files that can be used by the template as well as the components;
• /images/ - contains image files required by the template;
• /page_templates/ - contains page templates and a description in the file .content.php;
• /include_areas/ - contains files rendered as include areas on the pages;
and files:
• header.php - template prolog (header, see below);
• footer.php - template epilog (footer, see below);
• styles.css - specifies CSS styles for use on the site pages;
• template_styles.css - contains CSS styles for use by the template itself;
• .menu type.menu_template.php - specifies the code to render the menus;
• chain_template.php - the code to render the navigation breadcrumbs;
• any other auxiliary files and folders.

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

• login;
• password;
• email.

Login and password are required to log in to the system. A user is always a member of a certain user group and has the permissions assigned to that user group.

• Apache - DocumentRoot parameter in the httpd.conf file;
• IIS - on the Home Directory > Local Path.

• downloads and installs system updates;
• downloads and installs new modules and updates for existing modules;
• downloads new localization files and new languages;
• performs licensing functions.

The update system performs the following steps when checking for updates:

• the remote server requests the product key;
• if the key check was successful, the update system checks if there are any updates available;
• creates a summary of updates and prompts a user to select the updates they want to install;
• downloads and installs the selected updates.

• ID;
• Name;
• Date and time format;
• Encoding;
• other fields.

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

The sum of these numbers is the actual set of permissions in each triad. For example, 6 is read and write, 7 is full access, 5 is read and execute.

Therefore, a complete Unix permission consisting of the three triads in numeric notation may look, for example, like this: 764. Here, 7 means the file owner has full permission (read, write and execute). 6 means the members of a user group whose member the owner is have read and write permission. Finally, all other users have read permission (4).

PHP permissions are always specified as octal numbers which means they must have a 0 (zero) prefix. For the previous example, the correct PHP permission is 0764.

In general, a prolog refers to the topmost part of a web page.

For public area pages, the prolog is unique to a site template and resides in the file /bitrix/templates/site_template_ID/header.php.

For Control Panel pages, the prolog is stored in the file /bitrix/modules/main/interface/prolog_main_admin.php.

The prolog can have service and visual portions. The service part defines the required classes (via the include expression), creates a database connection and instances of $USER, $APPLICATION, etc. The visual part emits code a visitor sees as the page header.

If your template has everything in a single file, use the call

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

If your template splits the service (prolog_before.php) и визуальную (prolog_after.php) and visual:

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

An epilog refers to the bottom part of a web page.

For public area pages, the epilog is unique to a site template and resides in the file /bitrix/templates/site_template_ID/footer.php.

For Control Panel pages, the epilog is stored in the file /bitrix/modules/main/interface/epilog_main_admin.php.

The epilog can have service and visual portions. The service part can perform a number of background actions: send emails, handle OnAfterEpilog events etc. The visual part emits code a visitor sees as the page footer:

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

If your template splits the service (epilog_before.php) and visual (epilog_after.php) parts, use two calls:

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

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