Bitrix Multilingualism: Site InfoBlocks in Different Languages. (Translator, Multilingualism)

- Security improved

Obsolete styles and the global menu image managed by bxproger.core have been removed.

Fixed the creation of translation tables for user fields during installation: now products, users, and other entities with user field tables are taken into account.

Added the ability to re-run the creation of missing tables and columns for the installed module.

- Minor fixes

Separate images for language versions of elements and sections have been added.

If a translation image is missing or deleted, the default language image is used.

Added cleanup of translation files when deleting entities and protection of used files.

Fixed translation cleanup when deleting a section: translations of elements with other bindings are preserved.

Security improved: access outside the site directory (path traversal) is blocked when connecting EDIT_FILE_BEFORE — the path is verified via realpath and must remain within the site root.

Security improved: validation of return_url before redirect is added — only local paths and addresses of the current site are allowed; javascript:, data: schemes and redirects to third-party domains are prohibited.

Security improved: protection against open redirect is applied to all copied admin pages of the infoblock.

Module security improved: SQL injections, cross-site scripting, and path traversal vulnerabilities when working with files have been eliminated.

Unsafe data deserialization and arbitrary file inclusion have been removed.

Fixed: Synchronization with 1C no longer loses the import step between requests — premature closure of the PHP session during import has been removed.

Improved: The consolidated translation statistics (informant and gadget) are now cached for 1 hour and are not recalculated with every change to elements and sections — database load has been reduced. Cache clearing occurs when module settings are saved.

Improved: The translation statistics informant is calculated only in the administrative section, not on the public part with the editing panel.

Changed: Automatic redirect to the translation language upon first opening a page has been removed — language switching is now manual.

Added separation between the translation viewing mode in the admin panel and the mode for writing to translation tables: writing to fan_translator_* occurs only when the hidden field MM_TR_IS_TRANSLATIONS=Y is sent from the editing forms.

Fixed: programmatic updates of elements, sections, and properties (agents, API, CLI, external tools) without this field now write to the base Bitrix tables again, not to fan_translator_*.

Fixed: auto-translation after saving and cleanup of orphaned property translations when updating base content are no longer blocked due to the language in the admin panel URL; the translation record is considered, not the UI mode.

Fixed: forced auto-translation via the MM_TR_AUTO_TRANSLATE checkbox when saving main content works independently of the lang parameter in the admin panel address.

Added hidden fields MM_TR_IS_TRANSLATIONS to the editing forms for elements, sections, information blocks, properties, highload records, warehouses, and measurement units when the translation mode is active in the interface.

Fixed: partial updates of an element translation (e.g., only ACTIVE or activity dates) without the NAME field: the name field in the element translation table is no longer considered mandatory during ORM writing.

Improved: updating highload records in translation mode: non-translatable user fields in the main HL table are filtered out only during explicit translation writing, as with information blocks.

Fixed: during exchange with 1C (CommerceML, mode=import), the import could be interrupted by a "Lock wait timeout exceeded (1205)" error when clearing element property translations.

Fixed: the same error occurred during cascading deletion of a section or elements in the admin panel if an exchange with 1C was running in parallel.

Improved: cleaning orphaned property translations and deleting element translations during 1C exchange are now deferred until the HTTP request completes — locks on b_iblock_element_property no longer conflict with the import transaction.

Improved: DELETE queries to property translation tables are now retried in case of short-term blocking (1205).

Added: TranslateMode class — unified translation mode logic on infoblock, section, and element edit pages.

Improved: when opening a card for the main language of an infoblock for the first time, it automatically switches to the first target translation language; manual lang switching within the same entity is now saved in the session and is no longer reset.

Improved: the page title in translation mode (Translate mode) is now rendered via TranslateMode::applyPageTitle() on infoblock, section, and element edit pages.

Added: In the settings of each information block, you can specify the Main language for automatic translation. Content is written and translated from the information block's language; if not specified, the module's main language is used.

Improved: Translate mode in the admin panel (header, hiding non-translatable properties, UF) now considers the information block's main language, not just the module's language.

Improved: Automatic translation (including after exchange with 1C) takes the source language from the information block settings under the same rules: when adding, based on the automatic translation list; when updating, when Forced automatic translation is enabled.

Improved: Display of Balance and authorization via the core API (support for the new balance/quota format).

Removed: Duplicate Settings item from the module menu (settings remain in the Module Settings section).

Important during update: For information blocks with content not in the module's language, open bxproger.translator settings, select the Main language for the relevant information block, and save.

Security update

Fixed the display of translator account data in the module settings: added escaping of values received from the external service.

Eliminated the possibility of executing HTML and JavaScript in the administrative section via an untrusted response from the translation service.

Added access rights verification for the Playground service page to prevent users without bxproger.translator rights from using module functions.

Conducted a repeated security check of the module according to Bitrix Marketplace requirements: remarks have been moved to the "fixed" status.

- Fixed an error of forced automatic translation of properties when changing infoblock elements

- Fixed compatibility with modules for custom infoblock properties and user fields HowTo and FAQ

- Improved the display of statistics for the "Site Translations" gadget

Added: translation readiness statistics for active sections and infoblock elements from module settings (by language).

Added: an informer in admin panel notifications with a battery indicator and translation percentage.

Added: the ability to temporarily hide the informer (Hide button).

Added: the Site Translations gadget to the admin dashboard — a summary of sections and elements, quick access to mass translation and settings.

Improved: caching of statistics for comfortable work with large catalogs.

Clarified: upon license expiration, new translation lines are not saved, while already saved translations continue to display correctly on the site as before.

Your already translated content remains available to visitors; license renewal is required only for further work with new translations.

Added: management of forced automatic translation has been moved to the module settings. Now, under the language selection for each information block, there is a checkbox 'Forced Automatic Translation' — when enabled, all element changes are re-translated upon each save.

Improved: it is no longer necessary to specify constants of the form FORCE_TRANSLATE_IB_ID_XX in the /bitrix/php_interface/init.php file — the old method via constants has been removed, and the mode is enabled directly in the Module Settings section.

Added: the 'Not included in automatic translation' flag for information block properties and user fields (UF). Marked properties and fields are excluded from automatic translation.

Improved: the exclusion checkbox is drawn directly in the standard property editing forms for information blocks and user fields, without replacing the forms themselves.

Important during update: if forced automatic translation was previously enabled via constants in init.php, mark the required information blocks with the 'Forced Automatic Translation' checkbox in the module settings — the previous constants are no longer taken into account.

Settings are located in the Module Settings section.

- Minor improvements

- Compatibility with uffaq and ufhowto modules

Added: support for DeepL glossary during automatic translation — when the DeepL Glossary (Translator) module is installed and a synchronized language pair is configured, the translation takes into account glossary terms.

Changed: login and authorization password are no longer set in the Multilingualism module settings — authorization is configured in the Core module (bxproger.core); the translator settings display a hint with a link.

Fixed: in the translation sandbox, service errors are correctly displayed, including authorization errors and API response errors.

Added: mass automatic translation of Highload-block records — new menu item in Multilingual: Mass Automatic Translation of Highload-blocks. In module settings, you can select HL-blocks for automatic translation and specify languages for each block. Support is provided for skipping already translated records and resuming from the last processed one.

Added: search index for infoblock section translations — when saving a section and during search reindexing, SEARCHABLE_CONTENT in the translations table is updated. Section search takes into account the translated name and description.

Fixed: saving translations in element and section editing mode — correct handling of custom user fields of type customhtml (including multiple ones) and customfaq, as well as smart filter hints FILTER_HINT for section properties.

Fixed: saving multiple element properties in translation mode — values are bound to original lines, new FAQ items are correctly added to the base properties table, and deleted translations are cleared without losing original data.

Fixed: automatic translation of Highload-blocks — metadata UF and values for translation are taken from the main HL entity, not from the empty mm_ut_* table, which previously caused automatic translation to skip fields.

Improved: unified mechanism for reading UF values from the form in translation mode via the OnResolveUserFieldPostValue event — easier to connect custom field types without modifying the module core.

Improved: normalization of property and UF values before writing to translation tables — correct serialization of HTML fields, files, and composite types, without unnecessary trim on serialized data.

Recommendations after update

In Module Settings, specify Highload-blocks and automatic translation languages, then test mass translation on a sample of records.

Test editing an element with multiple properties and FAQ in translation mode.

Test section search in translation languages — if necessary, reindex search in the site administration.

Important security update: vulnerabilities identified in the 1C-Bitrix Marketplace technical audit have been fixed — Authentication Bypass and Information Disclosure in the infoblocks AJAX endpoint, Stored XSS in module settings, Insecure Deserialization, and a potential RCE in dynamic compilation of HL entities. This update is mandatory for all users.

HL translation mode: fixed saving and reading of records (mm_hl_* tables, COALESCE for string UF, correct handling of multiple fields after retrieval).

Performance: reduced unnecessary database queries during compileEntity and getList (table check cache, single pass through UF, no unnecessary compilation of related HL via hlblock binding).

HL admin panel: non-translatable fields (file, HL binding, etc.) in translation mode are displayed in view-only mode without disk.scopeTokenService errors; files are shown as links via the standard upload mechanism.

Related HL blocks: it is recommended to compile reference dictionaries first, then the main block — otherwise, the PHP table class may be created by the core without translation support.

Recommendation: after updating, verify editing of an HL record in translation mode and the list of elements with multiple UF.

- Improved handling of custom fields in translation mode: fields that are not translatable (number, file, HL-block binding, etc.) are displayed in the administrative section for viewing only, with an explanation that the value is common to all languages. When saving a translation, such fields are not overwritten. The tooltip is localized into 14 interface languages of the administrative panel.

- Fixed saving of Highload-block records in translation mode: values of fields of the "Binding to Highload-block" type and other non-string UF fields are no longer lost upon update.

- Optimized translation tables mm_hl_* and mm_ut_*: only string translatable UF fields are created and updated in them. This reduces table size and eliminates data duplication for fields that are common across all languages.

- Fixed SQL query formation (COALESCE) when reading UF: translation substitution is performed only for string fields; other values are taken from the main entity table.

- Fixed adding a column for the customhtml user type to the infoblock sections translation table.

- Eliminated erroneous creation of service tables mm_ut_hlblock_* when adding UF to a Highload-block (for HL, only tables mm_hl_* are used).

- Unified mechanism for determining translatable UF (BASE_TYPE = string) for infoblock sections, Highload-blocks, auto-translation, and administrative forms.

- Fixed an error on the mass auto-translation page (admin panel) related to the use of the Catalog class. The module now works correctly in the Standard edition.

- Fixed an error where non-translated values of the 'Item Binding' property type were displayed in the bitrix:catalog.section component.

- The DataManager class has been improved.

- Minor improvements.