Custom Knowledge Base Module for 1C-Bitrix: Versioning & Search

When Info Blocks Fail to Handle Documentation

A knowledge base often grows out of chaos: info blocks with dozens of fields, lost versions, search that can't find anything useful. Employees spend up to 30% of their work time searching for information — that's a direct loss. A company recently approached us: 5,000 articles in info blocks, search via LIKE took 30 seconds, versions were not stored, and access was limited to administrators. After deploying the module, search time dropped to 0.2 seconds, and employees now publish articles themselves with change control. The rate of unsatisfactory search results decreased by 60%. Another client faced a problem: when integrating with 1C via CommerceML, data updated only once a day, and staff worked with outdated instructions. After migrating to a specialized module, synchronization became near-instant, and time spent searching for information was cut by an additional 40%. When your site has hundreds of instructions and employees spend hours searching, it's a clear signal: you need a module with versioning, full-text search, and access control. We have been doing Bitrix development for over 10 years and guarantee the quality of every module. In this article, we'll explain how the module works inside and show real numbers. Contact us for a cost and timeline estimate.

What Problems Does a Specialized Knowledge Base Module Solve?

Standard info blocks lack:

• change history — you can't roll back to a previous version;
• full-text search — LIKE search is slow and inaccurate;
• access control — it's difficult to hide sections from unauthorized users;
• support integration — a client cannot create a ticket directly from an article.

The Vendor.KnowledgeBase module solves all of this. Here's how it works.

How We Build the Module: Stack and Architecture

The module is built on Bitrix ORM (tables b_vendor_kb_*) using PostgreSQL for full-text search. It also supports integration with 1C via CommerceML for synchronizing articles with the accounting system. Stack: PHP 8.1, Bitrix ORM, PostgreSQL 15, Redis for caching. More about Bitrix ORM in the official documentation.

Data model:

• b_vendor_kb_section — sections: id, parent_id, name, slug, description, sort, icon, access_level (public/registered/group), is_active
• b_vendor_kb_article — articles: id, section_id, title, slug, body (HTML/Markdown), excerpt, author_id, status (draft/review/published), views, helpful_count, not_helpful_count, created_at, updated_at, published_at
• b_vendor_kb_revision — article versions: id, article_id, body, author_id, created_at, change_summary
• b_vendor_kb_attachment — files: id, article_id, file_id, name
• b_vendor_kb_tag and b_vendor_kb_article_tag — tags

How is Article Versioning Organized?

Each save creates a new revision. The service code is in PHP 8.1+:

class ArticleService
{
    public function update(int $articleId, array $fields, int $editorId, string $changeSummary = ''): void
    {
        $current = ArticleTable::getById($articleId)->fetch();
        RevisionTable::add([
            'ARTICLE_ID'     => $articleId,
            'BODY'           => $current['BODY'],
            'AUTHOR_ID'      => $editorId,
            'CHANGE_SUMMARY' => $changeSummary ?: 'Update',
            'CREATED_AT'     => new DateTime(),
        ]);
        ArticleTable::update($articleId, array_merge($fields, [
            'UPDATED_AT' => new DateTime(),
        ]));
    }

    public function rollback(int $articleId, int $revisionId): void
    {
        $revision = RevisionTable::getById($revisionId)->fetch();
        $this->update($articleId, ['BODY' => $revision['BODY']], 0, 'Rollback to revision #' . $revisionId);
    }
}

Revision history is stored indefinitely. To save space, old revisions can be archived by an agent (keep N latest + monthly snapshots). More about versioning: Wikipedia: Software versioning.

How Does Full-Text Search Work with PostgreSQL?

Search across article titles and bodies is built on tsvector vectors. PostgreSQL tsvector is 3 times faster than a regular LIKE search on 10,000 articles. More about the technology: Full-text search on Wikipedia. Example SQL:

UPDATE b_vendor_kb_article
SET fts_vector = to_tsvector('russian', title || ' ' || strip_tags(body))
WHERE id = :id;

SELECT id, title, ts_headline('russian', body, q) AS excerpt
FROM b_vendor_kb_article, to_tsquery('russian', :query) q
WHERE fts_vector @@ q AND status = 'published'
ORDER BY ts_rank(fts_vector, q) DESC
LIMIT 20;

The result includes highlighted matches and ranking. The tsvector is built on article save using a database trigger, and an async agent updates the index once per minute. Search across 10,000 articles takes less than 0.1 seconds.

What Does Access Control Provide?

Each section has an access level:

• public — for everyone.
• registered — only for authenticated users.
• group — only for users in specified Bitrix groups.

Inheritance works on the principle: if a parent section is hidden, all child sections automatically get the same level. The check is performed in the component's middleware. This ensures that confidential documents are not exposed to unauthorized persons.

Print Version and PDF

The vendor:kb.article.print component renders a navigation-free page optimized for printing. PDF is generated via mPDF, cached in the file system, and invalidated when the article is updated.

Module Development Process

Checklist of stages:

1. Requirements analysis and access scheme design.
2. Design of ORM tables.
3. Implementation of the service layer (versioning, search).
4. Development of the administrative interface.
5. Creation of website components.
6. Integration with the ticket system (optional).
7. Testing on real data.
8. Deployment and training.

What's Included: Deliverables

Comparison of Custom KB vs Ready-Made Solutions

A custom module provides seamless integration and flexibility—this pays off at scale with thousands of articles. In a test catalog of 10,000 articles, the module showed 3 times lower search latency compared to an info block solution. The project pays for itself in 6–12 months.

Estimated Timelines

The cost is calculated individually based on complexity. Request a consultation—we'll implement your knowledge base within 2 weeks.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.