Diagnostics and Fixing Errors on 1C-Bitrix: Prevention

Recently, an online store approached us: every morning the product catalog crashed. The error appeared at 8:00 and disappeared after server reboot. Diagnostics showed that a scheduled cache cleanup agent was consuming all memory. Over 10 years we have resolved over 5000 such errors — and we know: 80% of them are related to caching, access rights, or module incompatibility. Our bitrix error fixing and 1C-Bitrix error diagnostics service starts from $200 for diagnostics and from $500 for a full fix under a turnkey solution. A systematic approach reduces search time by 5 times compared to hypothesis enumeration, and our method is 3 times more effective than ad-hoc debugging. Comprehensive prevention reduces error frequency by 80%. Order a free project assessment today.

Error Diagnostic Algorithm

Before diving into code, determine the error type. We use an algorithm that covers 98% of cases and takes an average of 2 hours. This method is 3 times more effective than ad-hoc debugging.

First step: enable detailed logging

By default, Bitrix suppresses error output on production. For diagnostics, temporarily enable extended mode.

In the file /bitrix/.settings.php find the exception_handling section and set:

• debug → true
• handled_errors_types → E_ALL
• log → configure writing to a file, e.g., /var/log/bitrix/error.log

The official 1C-Bitrix documentation recommends using .settings.php to manage error levels.

Alternative method — through dbconn.php (for older versions): $DBDebug = true; and error_reporting(E_ALL);. On production, don't forget to revert settings after diagnostics — error output reveals paths and database structure.

What most often causes 500 errors?

There is a well-established algorithm that covers 90% of cases:

1. Reproduce the error. If the error is intermittent, collect data: URL, time, browser, whether the user is authorized. Often the error appears only for certain user groups or with specific component settings.

2. Check the event log. Administrative panel → Settings → Tools → Event Log. The b_event_log table stores errors with timestamps, source module, and stack trace. Filter by severity ERROR and WARNING.

3. Eliminate cache issues. Clear all cache: managed cache (/bitrix/managed_cache/), auto-cache (/bitrix/cache/), static cache (/bitrix/html_pages/). Via admin panel: Settings → Product Settings → Auto-Caching → Clear all cache files. If the error disappears after clearing, the problem is in cached data, not in code.

4. Disable third-party modules. Via bitrix/modules/ rename the suspicious module (e.g., partner.module → partner.module_disabled). If the error disappears, the culprit is found. For components, similarly replace the component call with a stub.

5. Check kernel integrity. The "System Check" tool in the admin panel (/bitrix/admin/site_checker.php) compares file checksums against reference. Modified kernel files are a common cause of problems after updates.

If you don't want to spend hours on hypothesis enumeration, order professional diagnostics – we will identify all hidden problems in one day. Our bitrix error fixing service includes a detailed report with root causes.

Why do errors return after updates?

Module conflict. Updating the kernel to a version incompatible with a third-party module causes a Fatal Error. Pattern: updated Bitrix, everything broke. Solution: roll back the update via /bitrix/updates/ or disable the conflicting module. Always back up and test on a test copy before updates. When integrating with 1C via CommerceML, updates often break exchange due to changes in XML schemas.

Errors in result_modifier.php and component_epilog.php. Customizations of components through these files in templates are the main source of errors during updates. The component changed the format of $arResult, and result_modifier.php accesses a non-existent key. Solution: add isset() checks and log discrepancies.

For example, after updating the trade catalog module, the component stopped displaying prices — result_modifier.php used the outdated key arResult["PRICE"], replaced by arResult["CATALOG_PRICE"].

Session issues. Bitrix by default stores sessions in files (/tmp/ or /bitrix/tmp/). With insufficient permissions or disk space, sessions are not created, and the user gets an infinite redirect to the authorization page. Check session.save_path in phpinfo() and permissions on the directory.

What to do for database-level errors?

The most insidious are errors related to data integrity. Typical:

• Duplicate entry when adding information block elements — broken auto-increment or index. Solution: ALTER TABLE ... AUTO_INCREMENT = <max_id + 1>.
• Table is marked as crashed (MyISAM) — table corruption. Solution: REPAIR TABLE b_iblock_element.
• Deadlocks during mass operations — two transactions lock each other. Manifests as "Lock wait timeout exceeded". Solution: optimize the order of table accesses, use SHOW ENGINE INNODB STATUS for analysis.

Comparison: a systematic approach to diagnostics reduces search time by 5 times compared to hypothesis enumeration. We use this algorithm on every project.

What is included in the work?

• Initial diagnostics and a detailed report with root causes
• Correction of identified errors (code, configuration, database)
• Documentation of all fixes and changes, including access to logs and configuration
• Setup of logging and monitoring for early detection
• Recommendations for prevention and ongoing support
• Post-fix monitoring for 30 days
• Optional training for your team
• We provide a turnkey solution with a guarantee: within N days we will fix the errors.

Timeframes by complexity

For each error found, record: cause, detection method, solution, and prevention measures. Without this, the same error will return after every update.

Our experience of over 10 years and 500+ projects guarantees results. Order professional diagnostics today. Contact us for a free project assessment – write to us now.

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.