What this solution does
The Xlogic Universal Combined InfoBlock Property module is designed for projects where content does not fit the 'one field = one value' model. It enables the creation of flexible data structures by allowing you to configure a set of subfields for specific business tasks and manage them within a single convenient form. This eliminates the need for extra info blocks, complex workarounds, and loss of control over data structure.
The solution is suitable for service websites, catalogs, corporate portals, landing pages, and content-rich projects where rapid deployment of new page formats is required while maintaining clean data architecture.
Key capabilities of the module:
- Combines related data into a single logical field with JSON storage.
- Allows building custom structures from subfields of various types.
- Accelerates content manager workflows through an intuitive admin interface.
- Reduces development costs: structure changes are made via property settings without creating new entities.
- Preserves layout flexibility: data is ready for arbitrary output in templates.
Supported subfield types:
- String
- Number
- File
- Text (including multiline input and HTML editor)
- Date
- Element reference
- Section reference
- List
- Color
- Yandex.Map
Key use case: building block-based page structures.
The xlogic.iprop module is designed to create universal combined properties for information blocks. The primary use case is building pages from semantic blocks such as 'Who is it for', 'Work stages', 'Cost', 'Work examples', 'Frequently asked questions', 'Advantages', and 'Specifications'. Each block is implemented as a separate property containing a set of subfields: title, description, image, list, link, date, references, and others.
Project benefits:
Eliminates the need to create dozens of standard information block types.
Allows page structure to adapt to specific sections or products.
Keeps content manageable and predictable for editors.
Provides the frontend team with clean structured data for any layout.
Scenario 1: Contacts
The module is convenient for cards of branches, offices, sales points, and showrooms. Recommended data structure:
Address — text field.
Map — Yandex.Map (available only for the information block element).
Phone — text field.
Email — text field.
Benefits: a unified format for contact data, fast editing by managers, and a ready foundation for displaying contact blocks in the required design.
Scenario 2: Events
The solution is suitable for announcements of events, webinars, presentations, and training programs. Recommended data structure:
Start date — date field.
End date — date field.
The universal combined information block property by Xlogic enables the creation of structured data for various scenarios.
For event cards, it is recommended to use a text field for the venue and an element binding for the organizer. This ensures a clear structure, convenient filtering, and a unified standard for all events on the site.
For commercial offers, such as tariff grids, service packages, and promotional offers, the recommended structure includes the tariff name as a string, price as a number, service composition as multi-line text or a list, and tags like 'Hit' or 'Recommended' as a list. This approach allows transparent tariff management without a separate complex catalog, rapid updates to prices and composition, and convenient display in cards and landing pages.
Code examples are provided for developers to quickly integrate into Bitrix templates. When working with a single information block property (MULTIPLE = N), the value is received as an array of subfields. The example demonstrates retrieving contact data, checking for its existence, and displaying the address using the htmlspecialcharsbx function for safe output.
The Xlogic module implements a universal combined information block property. The code demonstrates the logic for rendering contact data and processing multiple properties. If the phone field is not empty, a call link is generated; if the email field is not empty, a mailto link is created. Elements are displayed only when corresponding values exist.
Example 2. Processing an information block element with a multiple property (MULTIPLE = Y). The property value is passed as an array of strings, where each string is a separate data block containing subfields. The script checks if the value is an array and if it is not empty. If the check fails, rendering stops. For each element in the array, fields are extracted: tariff name, price, list of services, and badge. The tariff name is rendered as a heading if it is not empty. The price is displayed with the ruble symbol if it is not empty and not null.
The Universal Combined Information Block Property by Xlogic provides mechanisms for safe data rendering in templates. Code examples demonstrate handling of various field types. For text data, the logic includes a conditional check for value presence before outputting the content with special character escaping. In the case of file subfields storing a numeric file ID, the system retrieves the file array via the CFile::GetFileArray method, verifies the existence of a source link, and generates a link to the file displaying its name. The example for section custom properties shows rendering event metadata: start date, end date, location, and organizer ID. All values are output with safe processing and type casting.
The Universal Combined Information Block Property by Xlogic allows storing structured data in a single field, simplifying content management. For stable operation, it is recommended to use immutable subfield codes such as TITLE, PRICE, and DATE_FROM, and avoid changing them without necessity. When outputting data in public templates, always apply escaping via htmlspecialcharsbx. For complex blocks, move JSON parsing logic to the result_modifier.php file, leaving only display operations in template.php. Repeating sections are conveniently implemented using multiple properties with a single rendering template.
This approach benefits business by accelerating the launch of new pages and directions, reducing development and maintenance costs, ensuring a unified content standard across all site sections, minimizing editor errors, and facilitating project scaling as the assortment or services expand.
For developers, the solution offers convenience through structured data in a single property, simple integration into component templates, a reduction in the number of information blocks and technical debt, and the ability to evolve the project flexibly without complex migrations.
General iT can install “Universal combined information block property”, configure its settings and verify its operation in the existing project.