Custom Classified Ads Board Development on 1C-Bitrix

Custom Classified Ads Board Development on 1C-Bitrix

A classifieds board is not just a "product list." Users create content, requiring moderation, flexible search with filters, status and expiration management. Without a ready solution, you have to build this logic from scratch. We have already implemented such projects, so we know the typical pitfalls: for example, search slowdown at 50,000 ads, or caching issues with a large number of VIP ads. The cost of fixing these mistakes can be comparable to the initial development, so it's crucial to lay the correct architecture from day one.

Our approach is to use infoblocks, HL-blocks, components 2.0, and tagged caching. According to official documentation, component 2.0 allows caching of individual template parts, which is critical for performance. In this article, we'll break down the key blocks of a classifieds board: from data structure to the expiration agent.

How is the infoblock structure for ads?

The infoblock is the main storage. Symbolic code: classifieds. Type: ADS. Required properties:

Infoblock sections — ad categories (Transport, Real Estate, etc.). Section hierarchy — tree via b_iblock_section. This structure ensures fast search and filtering by categories.

User ad submission: step-by-step

The add form is at /ads/add/. Process consists of several steps:

1. Authorization: if not logged in, redirect to /auth/.
2. Form filling: user enters title, description, price, category, uploads photos.
3. Validation: check required fields, phone format, image sizes.
4. Send to moderation: ad is saved with ACTIVE='N' and status MODERATION; moderators receive notification.
5. Confirmation: after successful save, user sees success message.

Key point: user uploads content — need spam protection and mandatory moderation.

// /local/components/local/ads.add/class.php

namespace Local\Ads;

class AdsAddComponent extends \CBitrixComponent
{
    public function executeComponent(): void
    {
        if (!$GLOBALS['USER']->IsAuthorized()) {
            LocalRedirect('/auth/?backurl=/ads/add/');
            return;
        }

        if ($this->request->isPost() && check_bitrix_sessid()) {
            $this->addAd();
        }

        $this->includeComponentTemplate();
    }

    private function addAd(): void
    {
        $el = new \CIBlockElement();

        // Process uploaded photos
        $photos = [];
        if (!empty($_FILES['PHOTOS']['tmp_name'])) {
            foreach ($_FILES['PHOTOS']['tmp_name'] as $i => $tmpName) {
                if (is_uploaded_file($tmpName)) {
                    $photos[] = [
                        'name'     => $_FILES['PHOTOS']['name'][$i],
                        'size'     => $_FILES['PHOTOS']['size'][$i],
                        'tmp_name' => $tmpName,
                        'type'     => $_FILES['PHOTOS']['type'][$i],
                    ];
                }
            }
        }

        $adId = $el->Add([
            'IBLOCK_ID'      => CLASSIFIEDS_IBLOCK_ID,
            'NAME'           => htmlspecialchars($this->request->getPost('title')),
            'DETAIL_TEXT'    => htmlspecialchars($this->request->getPost('description')),
            'IBLOCK_SECTION_ID' => (int)$this->request->getPost('category_id'),
            'ACTIVE'         => 'N', // Initially inactive until moderation
            'PROPERTY_VALUES' => [
                'PRICE'      => (float)$this->request->getPost('price'),
                'DEAL_TYPE'  => $this->request->getPost('deal_type'),
                'PHONE'      => htmlspecialchars($this->request->getPost('phone')),
                'USER_ID'    => $GLOBALS['USER']->GetID(),
                'AD_STATUS'  => 'MODERATION',
                'EXPIRE_DATE' => date('d.m.Y', strtotime('+30 days')),
                'VIEW_COUNT'  => 0,
                'PHOTOS'     => $photos,
            ],
        ]);

        if ($adId) {
            $this->arResult['SUCCESS'] = true;
            $this->arResult['AD_ID']   = $adId;
            // Notify moderators
            $this->notifyModerators($adId);
        } else {
            $this->arResult['ERROR'] = $el->LAST_ERROR;
        }
    }
}

How does ad moderation work?

The moderator page is a standard infoblock element list with filter AD_STATUS = MODERATION. Moderator actions change status and activity:

// Approve ad
$el = new \CIBlockElement();
$el->Update($adId, ['ACTIVE' => 'Y']);
\CIBlockElement::SetPropertyValues($adId, CLASSIFIEDS_IBLOCK_ID, 'ACTIVE', 'AD_STATUS');

// Reject with reason
\CIBlockElement::SetPropertyValues($adId, CLASSIFIEDS_IBLOCK_ID, [
    'AD_STATUS'     => 'REJECTED',
    'REJECT_REASON' => $reason,
]);
$el->Update($adId, ['ACTIVE' => 'N']);

// Notify user
$event = new \Bitrix\Main\Mail\Event([
    'EVENT_NAME' => 'AD_MODERATION_RESULT',
    'LID'        => SITE_ID,
    'C_FIELDS'   => [
        'AD_ID'  => $adId,
        'STATUS' => $status,
        'REASON' => $reason,
    ],
]);
$event->send();

The moderator can also edit the ad, change price or category. All actions are logged.

Search and filtering

Ad filtering is a critical part of UX. For simple searches — standard CIBlockElement::GetList() with filter. For high-traffic projects (over 100,000 ads) — Bitrix faceted search (search module) or ElasticSearch integration. Faceted search is 3–5 times faster than standard for complex filters.

Example filter with price range:

$filter = [
    'IBLOCK_ID'  => CLASSIFIEDS_IBLOCK_ID,
    'ACTIVE'     => 'Y',
    'SECTION_ID' => $categoryId,
    '>PROPERTY_PRICE'  => $priceMin,
    '<PROPERTY_PRICE'  => $priceMax,
    'PROPERTY_CITY'    => $cityId,
    'PROPERTY_AD_STATUS' => 'ACTIVE',
];

$sort = ['PROPERTY_IS_VIP' => 'DESC', 'DATE_ACTIVE_FROM' => 'DESC'];

VIP ads always on top by sorting IS_VIP DESC. At 500,000 ads, we recommend using a search index with incremental updates.

Ad expiration

An agent checks expired ads once a day. Agent registration and processing method:

// Register agent in /local/php_interface/init.php
\CAgent::AddAgent(
    'Local\\Ads\\ExpireAgent::run();',
    'local.ads',
    'N',
    86400, // Once daily
);

// Agent method
class ExpireAgent
{
    public static function run(): string
    {
        $today = date('d.m.Y');
        $result = \CIBlockElement::GetList(
            [],
            [
                'IBLOCK_ID'         => CLASSIFIEDS_IBLOCK_ID,
                'ACTIVE'            => 'Y',
                '<PROPERTY_EXPIRE_DATE' => $today,
            ],
            false,
            false,
            ['ID', 'PROPERTY_USER_ID']
        );

        while ($ad = $result->Fetch()) {
            $el = new \CIBlockElement();
            $el->Update($ad['ID'], ['ACTIVE' => 'N']);
            \CIBlockElement::SetPropertyValues($ad['ID'], CLASSIFIEDS_IBLOCK_ID, 'EXPIRED', 'AD_STATUS');
            // Notify user
        }

        return 'Local\\Ads\\ExpireAgent::run();';
    }
}

For a catalog of 1,000,000 ads, the agent may run longer than 5 minutes. In such cases, we run the agent in batches of 1000 records and use locking.

User personal cabinet

Page /personal/ads/ — list of current user's ads:

$myAds = \CIBlockElement::GetList(
    ['DATE_CREATE' => 'DESC'],
    [
        'IBLOCK_ID'       => CLASSIFIEDS_IBLOCK_ID,
        'PROPERTY_USER_ID' => $GLOBALS['USER']->GetID(),
    ],
    false,
    ['nPageSize' => 20],
    ['ID', 'NAME', 'ACTIVE', 'PROPERTY_AD_STATUS', 'PROPERTY_EXPIRE_DATE', 'PROPERTY_VIEW_COUNT']
);

User actions: edit, deactivate, prolong (if expired), delete. Also displays view and contact statistics.

View counter

On each detail page open — increment counter. Via AJAX to not slow initial render and avoid bots: send POST request with ad_id, get current value via CIBlockElement::GetProperty, update PROPERTY_VIEW_COUNT. For high-traffic projects (over 10,000 views per hour), we recommend async queue or Redis to avoid blocking writes on each view.

What is included in the work?

When ordering a turnkey classifieds board, we provide:

• detailed technical specification with prototype;
• infoblock, HL-block, and agent configuration;
• custom components and AJAX handlers development;
• integration with payment systems and delivery services (CDEK, Russian Post);
• documentation and staff training;
• 2 weeks of warranty support after launch.

Development timelines

Contact us for a consultation and precise estimate of your project. Our engineers have 5+ years of experience in 1C-Bitrix development and guarantee data security. Order a classifieds board that will perform reliably under load and generate profit.

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.