Аккаунт в General iT
Войдите или создайте аккаунт для управления услугами в панели.
MODULE FOR 1C-BITRIX
Vintra
The Data Import from External Sources to Information Blocks module automates the extraction of data from third-party systems into Bitrix information blocks according to a scheduled timetable. The base package includes the Yandex Maps source.
The Data Import from External Sources to Information Blocks module automates the extraction of data from third-party systems into Bitrix information blocks according to a scheduled timetable.
The base package includes the Yandex Maps source. It extracts public organization reviews, preserving the author, text, rating, publication date, avatar, and link to the original, along with aggregated data on the average rating and total review count.
The module architecture is built on the SourcePlugin framework, allowing functionality expansion through separate plugins. Available modules include wintra.connector-2gis, wintra.connector-sbis, wintra.connector-b24, and wintra.connector-travelline. These are released separately and activated via subscription.
A universal mapping mechanism with macro support is used for configuring data transfer. Supported macros include: {value}, {value|date:d.m.Y}, {value|trim}, {value|truncate:200}, {value|strip_html}, {value|upper}, {value|lower}. Cross-references {PROPERTY_X.value} are also available for concatenating values from different rules.
Data filtering on the source side is supported. For example, for Yandex Maps, it is possible to configure selection to include only reviews with a rating of 4 or higher.
Synchronization management is handled through a dedicated administrative panel page. A separate Bitrix agent is configured for each source with an individual update interval: 5 minutes, 15 minutes, one hour, or one day.
The module provides idempotent synchronization of data from external sources into information blocks. Repeated execution prevents duplicates by using a unique source ID and field hash: new records are added, modified records are updated, and unchanged records are skipped. Every run is logged with details on the number of fetched, created, updated, and skipped records, along with any errors; this information is available on the schedule page.
Version 1.1.0, released on July 14, 2026, introduces a VKontakte plugin. This feature enables broadcasting news from a community wall to an information block. Authentication is performed via VK ID using OAuth, with automatic token refresh. The plugin supports transferring text, dates, counters, photos, and videos with an embedded player. It allows filling multiple and file properties of information blocks, including gallery creation. A macro for line breaks in HTML content has been added.
Typical use cases:
Yandex Maps reviews on the website. After connecting the source and specifying the company card URL on Yandex Maps, select the target information block named 'Reviews'. Configure the mapping: Author → NAME, Text → PREVIEW_TEXT, Rating → PROPERTY_RATING, Date → ACTIVE_FROM, Avatar → PREVIEW_PICTURE. Setting a filter for '4+' and a schedule of 'once per hour' ensures automatic delivery of reviews to the website.
Importing clients from Bitrix24 into the catalog. Using the wintra.connector-b24 plugin, client cards from the CRM are automatically written to the 'Clients' information block and displayed on the website in the 'Our Clients' section.
Import services from SBIS into the site's services info block. The wintra.connector-sbis plugin is required for this functionality.
General iT can install “Import of data from external sources into information blocks”, configure its settings and verify its operation in the existing project.
UPDATE HISTORY
Unused handler address removed from the distribution. The file admin/ajax.php and its page in the administration panel were never called from anywhere — neither from the module code nor from page scripts. At the same time, the address accepted credentials of the connected source and transmitted them outward, and was the only point in the module without demo-mode verification. An unnecessary address that no one opens still requires monitoring, so it has been removed; during updates, the files are also removed from already installed sites.
Fallback texts have been translated into Latin characters. The demo-mode panel label, the module not connected message, and the fallback module name were written in Russian in the code. The marketplace archive is assembled in cp1251 encoding, and on the site in UTF-8 such text appears as question marks. These lines are visible only when the language file fails to load for some reason — that is, precisely when something is already wrong, and a readable message is most needed.
Internal files are no longer included in the distribution. Since the module has no separate source folder, the CHANGELOG.md file ended up in archive 1.1.5, and during a full build, our other documents would have been included as well. A build exclusion list has been added.
The demonstration mode is visible in the module. A standard Bitrix banner with a countdown has appeared on the module pages: "Module demonstration mode. Days remaining: N" with a link to purchase. Previously, the countdown was visible only in the list of installed solutions, and the customer would only learn about the end of the demo after the fact.
A clear message after the demo ends. When the demonstration period has expired, the module pages display the reason and a link to activate instead of an empty page.
Record selection filter. A filter "Load only if the field is filled" has been added to the source settings: records with an empty selected field are skipped. For example, VKontakte posts without text no longer create empty news items.
Header mapping. A composite header is generated even for records with an empty source field — a post without text no longer causes the run to fail with the error "required field Title is not filled". If the name is still empty, the record ID is used instead.
Source fields in transformations. Any source field can be inserted in a transformation by its code (e.g., {post_id}), without creating a separate property for it. The order of rules does not matter.
Security. Debug logging to the event log has been completely removed. The token encryption key is now random: it is generated upon the first save and stored in a protected site file, not exposed via public parameters. VKontakte connection via OAuth is protected against CSRF. External font loading has been removed from the sources page.
Info block section selection. After selecting the info block in the source settings, you can specify the section where records will be stored (e.g., "News"). Records are created and updated in the selected section; by default, this is the root.
Security (full audit). Technical details of errors (source connection check, info block property creation, source copying, data retrieval error) are not displayed externally — they go to the event log, and the user is shown a generalized message.
Interface encoding. Separators (characters "·" and "—") in breadcrumbs, the "Help" section, and run statuses are formatted as HTML entities and ASCII — they no longer get corrupted on UTF-8 encoded sites.
Security (Marketplace moderation notes). Technical details of exceptions (VK ID token exchange, ajax handler) are no longer displayed externally — they go to the event log, and the user is shown a generalized message. The debug log and legacy agent write only to the event log (via the debug flag), not to a file in the site root.
Encoding. Characters outside cp1251 have been removed from the interface and code: arrows and crosses are formatted as HTML entities, and breadcrumbs and field mapping tables no longer get corrupted on cp1251 sites.
Plugin "VKontakte" (news). Broadcasting posts from a community wall to an information block. Authorization via VK ID (OAuth 2.1 + PKCE): the client specifies only their application ID; the module obtains and refreshes access tokens itself, storing them encrypted for each source. Uses the "wall.get" method. Source fields: post text (raw and with line breaks), date, likes, comments, reposts, views, post link, post ID, cover image, all photos, videos (link + embeddable player).
Filling multiple and file properties. Mapping distributes a list of values across lines; for a "File" type property, each image is uploaded via an SSRF filter. The post's photo gallery is placed into the information block's multiple gallery property.
The "nl2br" transformation macro converts line breaks into HTML line breaks, preventing text from merging.
Run diagnostics. Element creation failures are no longer hidden as "skipped": the status displays the count of records not created and the reason provided by Bitrix.
Restoration of deleted elements. If an element is manually deleted from the information block, the next run recreates it instead of attempting to update a non-existent record.
Security (Marketplace scan). Technical details of exceptions (VK ID token exchange, AJAX handler, debug log) are no longer exposed externally; they are sent to the event log, and the user sees a generalized message. The debug log has been switched from a file to the event log.
Affected files: "lib/Plugins/Vk/" (new plugin), "lib/Core/MappingEngine.php", "lib/Core/Scheduler.php", "lib/Core/PluginRegistry.php", "include.php", "admin/sources.php", "install/index.php", "install/tools/" (OAuth handler), "lang/ru/", "docs/public/plugins/vk.md".
Fixes based on Marketplace moderation feedback: - The solution name after installation has been standardized to the marketing title "Import of data from external sources into information blocks" ("MODULE_NAME"). The module UI brand has been unified as "Vintra.WebConnector"; previously, an inconsistent variant "Vintra.Connector" appeared in the interface (menu, headers, installation titles, help). - Post-installation message: characters outside cp1251 (typographic arrows and icon symbols in buttons) have been removed from language strings; during archive packaging, these were turning into "?". Affected are the installation step text and the source list buttons (Run, Save and run, Copy, To list). - "Help" section: the manual loading has been fixed. "user-help.md" is now placed at the actual distribution path of the hub docs ("docs/public/"; previously the URL returned 404). The loader now checks the HTTP response status and, if not 200, displays an embedded copy of "install/help.md" instead of the error page body.
Reliability: the "Help" page checks "Loader::includeModule" and displays a clear message instead of the fatal error "Class ... PageHeader not found" in case of installation desynchronization.
Affected files: "lang/ru/install/index.php", "lang/ru/install/step.php", "lang/ru/install/unstep2.php", "lang/ru/admin/sources.php", "lang/ru/admin/schedules.php", "lang/ru/admin/menu.php", "lang/ru/install/admin/wintra_connector_help.php", "install/admin/wintra_connector_help.php", "install/help.md", "docs/public/user-help.md", "install/version.php".
Security fix (Marketplace security-scan): - AuthManager: plaintext-fallback ("plain:" prefix) removed when storing credentials. Now, even without an explicit key in ".settings_extra.php", a fallback key derived from "document_root + Bitrix license-key" is used — data is encrypted with AES-256-CBC in any case. Previous "plain:" entries are transparently decrypted once and rewritten as "aes:" on the next "encrypt()" call. - MappingEngine::resolveImage (SSRF): before downloading an image, the IP of the target host is checked. Private/loopback/link-local/AWS metadata ranges are blocked (RFC1918, 127.0.0.0/8, 169.254.0.0/16, etc.). A size limit of 5 MB and "max_redirects=3" added — protection against resource-exhaustion. - Scheduler::dbgLog (information_disclosure): debug log moved from "/upload/wintra-connector-debug.log" (web-accessible folder) to "/bitrix/wintra-connector-debug.log" (protected by Bitrix ".htaccess"). The log is still written only if the flag file exists. - schedules.php auto-sync (mass_assignment-CSRF): agent sync for sources now triggers every 60 seconds (throttled via "b_option"), not on every load. CSRF cascade INSERT/DELETE in "b_agent" eliminated. - wintra_connector_help.php (remote_content_inclusion): markdown loading from hub.wintramedia.ru — size limit 512 KB + "max_redirects=3". A bundled fallback "install/help.md" added directly in the module archive: if the hub is unavailable or content exceeds the limit, the local copy is displayed.
Affected files: "lib/Core/AuthManager.php", "lib/Core/MappingEngine.php", "lib/Core/Scheduler.php", "admin/schedules.php", "install/admin/wintra_connector_help.php", "install/help.md" (new), "install/version.php".
YOUR PROJECT INFRASTRUCTURE
FROM THE SAME DEVELOPER
Vintra
The module assembles images from layers with live preview, inserts data from information blocks, applies PHP transformations, and saves the result to the product card or an information block property for further use on marketplaces, advertising systems, and other services.
The 'Wintra.Redirects' module redirects visitors and search engines from old site URLs to new ones, preventing 404 errors when pages or sections are moved. This preserves search engine rankings by automatically transferring accumulated positions to the new addresses. Capabilities Support for 301 and 302 redirects.
Wintra.ImageOptimize The module provides copies of images in WebP format. Links in the page HTML code point to optimized copies stored in a separate /upload/ directory. Original files are not modified; the module only reads them, performing no compression, resizing, or renaming. Copies are created on demand.
MORE FOR YOUR WEBSITE
The CleanTalk anti-spam module provides multi-level website security without the need for CAPTCHA. The system automatically blocks bot registrations, spam comments in forums and blogs, and spam in Progressive Media tree comments. Protection extends to private user messages, product reviews in 1C-Bitrix modern online stores, order forms, and any custom forms.
The SMSBiz module is designed for sending SMS notifications in online stores and corporate portals built on the 1C-Bitrix platform. Installation and use do not require programming skills and take only a few minutes. The solution is based on the SMSInt service, which has been operating in the market for over 15 years.
The 'MySklad: Extended Integration' module by Aprix.ru enables configuration of synchronization for products, orders, counterparties, payments, and shipments. Separate video tutorials are available for each area. A general overview video is also provided. Full technical documentation is available in the relevant section.
BEFORE YOU ORDER