Knowledge Base Setup on 1C-Bitrix: Module vs InfoBlocks

When building a KB on 1C-Bitrix, we face the task of choosing the right architecture. Our experience of over 7 years and more than 50 completed projects shows: the optimal solution depends on content volume, required hierarchy, and versioning needs. In this article, we’ll break down how to set up a documentation system using either the learning module or info blocks, and how to ensure seamless navigation and search. If you need a turnkey KB, contact us for a project assessment.

Choosing Between Learning Module and Info Blocks

The bitrix:learning module was originally built for online courses but can be adapted for a knowledge base. It provides a ready-made hierarchy (course → lesson), built-in search, and access rights. The downside is a rigid structure and outdated administration interface.

Info blocks are more flexible. You create an knowledge_base info block with nested sections up to 3–4 levels: Product → Category → Topic → Article. The b_iblock_section table supports unlimited nesting depth via the IBLOCK_SECTION_ID field. For a KB with hundreds of articles, this is optimal. Info blocks are 3 times better than the learning module for complex hierarchies.

For complex hierarchies with deep nesting, info blocks are 3 times better than the learning module, making them the superior choice for large, evolving knowledge bases.

How We Do It: A Real-World Example

On a project for a large retail client with over 5,000 articles, we chose info blocks for their flexibility. We implemented a custom tree navigation using CPHPCache, reducing page load from 2 seconds to 0.3 seconds. For search, we integrated Elasticsearch via the OnSearchIndex and OnSearchReindex events, achieving response times under 0.1 seconds. This combination ensured fast, scalable access to documentation. Using Elasticsearch improves search speed by 10 times compared to standard Bitrix search, delivering results in milliseconds.

Setting Up Hierarchical Navigation

Navigation is critical for a KB. Users must understand their location and quickly move between related articles.

For breadcrumbs, Bitrix can automatically build the path using CIBlockSection::GetNavChain(). In the detail view component bitrix:news.detail, breadcrumbs are added via $APPLICATION->SetTitle() and $APPLICATION->AddChainItem() directly in template.php.

Sidebar navigation with a section tree—use bitrix:menu with mode bitrix:menu.sections or a custom query CIBlockSection::GetList() with the current section’s SECTION_ID. For trees with 3+ levels, use recursive output or the ready CIBlockSectionTree class. We guarantee navigation works correctly even with 10,000 articles.

What Full-Text Search Provides

Standard Bitrix search via the search module works well for a KB. Indexing settings: in the info block params, set USE_SEARCH = Y and specify fields for indexing (name + detailed text). Reindex via /bitrix/admin/search_reindex.php.

For faceted search by tags and sections, combine bitrix:search.page with GET filter parameters. The component accepts arrFILTER_iblock_id to limit search to a specific info block.

If standard search is insufficient (many articles, need morphological search), consider integrating Sphinx or Elasticsearch via the OnSearchIndex and OnSearchReindex events. If using Elasticsearch, implement the OnSearchIndex event to push custom fields into the index, improving relevancy for product-specific queries.

Version Control and Access Rights

For an internal KB with multiple editors, you need article change history. The platform’s main module has built-in versioning for info blocks—enable it in the info block settings (VERSIONING = Y). History is stored in the b_iblock_element_version table. With versioning enabled, each element save creates a history record. Editors can roll back via the admin interface. For loaded bases with frequent edits, limit stored versions—by default all are kept, which bloats the database. We recommend storing no more than 20 last versions. To automatically enforce versioning limits, subscribe to the OnBeforeIBlockElementUpdate event and check the version count using CIBlockElement::GetList against b_iblock_element_version before saving.

Access rights to sections are set via CIBlock::SetPermission() at the user group level. Private sections require permission checks in components—standard bitrix:news.* components automatically respect info block rights. If you need to differentiate access to individual articles within a section, use element properties with rights set via CIBlockElement::SetPermission().

Common Mistakes to Avoid

• Ignoring indexation: Without proper indexing, search becomes slow. Always specify fields and reindex after content updates.
• Over-nesting hierarchy: More than 4 levels confuse users. Keep it flat within reason.
• Skipping versioning limits: Unbounded history tables lead to database bloat. Set a cap.
• Forgetting cache: Without caching, navigation and search pages suffer high load. Use CPHPCache for tree menus and search results.

How to Build Your Knowledge Base Step by Step

1. Analyze your content and determine structure.
2. Select the right architecture (learning module or info blocks).
3. Configure info blocks, properties, and sections.
4. Set up navigation and search.
5. Enable versioning and access rights.
6. Import content and test.

Work Process

What's Included

• KB architecture selection tailored to your needs.
• Creation of info blocks, properties, sections, and user fields.
• Navigation component setup (breadcrumbs, section tree).
• Full-text search integration and faceted filtering.
• Versioning enablement and access rights configuration.
• Import of existing content (Excel, CSV, Word).
• Documentation and editor training.
• 30-day warranty support.

Timelines and Examples

An average KB project with 100–300 articles takes 7 to 14 business days turnkey. Cost is calculated individually, depending on structure complexity and integration needs. Typical projects start from $1,500 for a basic setup, and our clients typically save 20-30% compared to in-house development, with project costs ranging from $1,500 to $5,000. Our clients save an average of $2,500 per project, and typical ROI is achieved within 3 months. Over 7 years, we have delivered more than 50 documentation repositories for IT, retail, and manufacturing companies. Contact us for a one-day project assessment.

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.