FAQ Module Development for 1C-Bitrix

Custom FAQ Module Development for 1C-Bitrix

Imagine: a customer catalog with 500 questions, the standard bitrix:catalog.list outputs them all in one list, there is no answer search, and analytics are nonexistent. The user painfully searches for an answer, fails to find it, and leaves for a competitor. We encountered such a project on one of our cases — an online store with hundreds of questions about delivery, payment, and returns. The standard infoblock couldn't handle it: the page loaded slowly, editors spent hours on manual sorting, and managers received dozens of identical inquiries in chat. We developed a specialized module that solves these problems. Our experience with Bitrix spans over 10 years and 20+ implemented projects. The module uses ORM (object-relational mapping, Wikipedia) for data operations and supports full-text search.

Limitations of the Standard Infoblock for FAQ

An infoblock with 'question' and 'answer' fields is a quick fix but doesn't scale. The main pain points:

• No full-text search over answers — Bitrix search only looks through page titles.
• No grouping by categories with an accordion — all questions are dumped in one list.
• No analytics: which questions are searched for, which don't help.
• No 'Ask a Question' form right on the page.

A custom module closes all these gaps. It includes ORM models, AJAX search with highlighting, voting, microdata, and reports.

How We Solve These Problems

We build the module on Bitrix ORM (QuestionTable, CategoryTable, SearchLogTable). This gives strict typing, events, and convenient querying. Search is implemented via AJAX with filtering by %QUESTION% and %ANSWER%, and for high loads, a full-text index in MySQL/PostgreSQL.

How to Speed Up Search with Thousands of Questions?

Standard %LIKE% search in MySQL slows down with 1000+ records. In the module, we implement two levels:

1. Fast AJAX search — query via QuestionTable::getList() with filter %QUESTION% and %ANSWER% (up to 1000 records).
2. Full-text index — when migrating to PostgreSQL (or MySQL 5.7+), create an fts_vector column with tsvector, updated via trigger. Search with MATCH ... AGAINST is 10x faster than LIKE.

public function search(string $query): array
{
    $query = mb_strtolower(trim($query));

    SearchLogTable::add(['QUERY' => $query]);

    $result = QuestionTable::getList([
        'select' => ['ID', 'QUESTION', 'ANSWER', 'CATEGORY_ID'],
        'filter' => [
            'IS_ACTIVE' => 'Y',
            [
                'LOGIC' => 'OR',
                '%QUESTION' => $query,
                '%ANSWER'   => $query,
            ],
        ],
        'limit' => 10,
        'order' => ['IS_FEATURED' => 'DESC', 'VIEWS' => 'DESC'],
    ])->fetchAll();

    return array_map(fn($q) => $this->highlight($q, $query), $result);
}

What Does Schema.org Markup Give?

Schema.org FAQPage markup (Wikipedia: Schema.org) is generated automatically for each question. This allows Yandex and Google to display answers directly in the snippet, increasing click-through rates. Implementation inserts itemscope and itemprop into HTML. We integrated it into the output component with no extra configuration needed. Order the module with microdata and get a boost in organic traffic.

What's Included in the Module Development?

Development Timeline

Adding full-text search via PostgreSQL tsvector adds +1 day.

Example Implementation

When a question is opened, the counter increments:

QuestionTable::update($questionId, ['VIEWS' => new \Bitrix\Main\DB\SqlExpression('VIEWS + 1')]);

After reading, the user votes 'This helped' or 'Did not help'. Voting statistics are used for sorting (useful questions higher) and for rewriting unclear answers.

The accordion is implemented with <details>/<summary> — indexed by search engines, requires no JavaScript. If ?q=question-slug is present, the section opens automatically.

Schema.org FAQPage markup is generated automatically:

<div itemscope itemtype="https://schema.org/FAQPage">
  <div itemscope itemprop="mainEntity" itemtype="https://schema.org/Question">
    <h3 itemprop="name">How to process a return?</h3>
    <div itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer">
      <div itemprop="text">To process a return...</div>
    </div>
  </div>
</div>

Analytics and Reports

Based on b_vendor_faq_search_log, we build reports:

• Top queries with no results — what users search for but don't find.
• Most viewed questions over a period.
• Questions with a high percentage of 'did not help'.

This data helps editors improve content.

Step-by-Step Implementation of Full-Text Search

1. Create an fts_vector column in the questions table.
2. Write a trigger that updates fts_vector on insert/update.
3. Replace %LIKE% with MATCH ... AGAINST in the search() method.
4. Configure relevance using field weights (e.g., question weight > answer).
5. Test performance with 10,000 records.

Why Choose Us

• Official 1C-Bitrix documentation confirms the best practices we use.
• 10+ years of experience in Bitrix and Bitrix24 development.
• Certified specialists — we guarantee code quality and deadline adherence.
• Transparent process — you always see project status.
• 30-day post-delivery support — free admin training.

Assess your project — contact us for a consultation. We will calculate the cost and timeline. Get a personalized offer today.

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.