Dubovoi: SKU - grouping simple products as trade offers

Dubovoi: SKU version 6.4.32

Fixed the SKU index, images for unavailable variants, and remarks from the marketplace security check.

What's new:

- No new user scenarios have been added in this update.

What has been improved:

- Fixed saving of SKU parameters in the index and protection of the background rebuild from recording a snapshot of another group.

- Product images are saved for unavailable parameter combinations, while the link remains blocked.

- The license check data set has been reduced and documented; the service address is no longer hidden in the code.

- The Bitrix24 support widget loads only after an explicit click by the administrator.

- Price output in three templates has been switched to a single secure renderer.

- Swiper 11.1.14 is supplied locally with the module and is not loaded from an external CDN.

Why it is important to update:

- This update closes eight external security check remarks and retains fixes for the card and background index from versions 6.4.31–6.4.32.

What to do after updating:

- After installation, run the standard reindexing of SKU rules and wait for the queue to complete.

- Check the SKU switches, variant images, and opening of the support chat via the button in the center of the module.

- Additional installation of version 6.4.31 is not required; the update is cumulative relative to version 6.4.30.

Dubovoi: SKU version 6.4.30

Fixed installation of SKU component updates.

What's new:

- No new user scenarios have been added in this update.

What has been improved:

- Fixed overwriting of new components with old files during updates.

- Components and public files are re-delivered from the current build, including fixing the preview for version 6.4.29.

Why it is important to update:

- Restores correspondence between the installed module version and the components executed by the site.

What to do after updating:

- Check the preview of variants and transitions between products.

- Grouping rules and source product images remain unchanged.

Dubovoi: SKU version 6.4.29

Fixed the correspondence of variant images to the selected products.

What's new:

- No new user scenarios have been added in this update.

What has been improved:

- The variant preview is taken from the product that the link leads to, even if the group contains multiple products with the same SKU values.

- The active variant displays the image of the opened product.

- The issue of substituting an unrelated image when the selected product has no image has been resolved.

Why it is important to update:

- Eliminates the mismatch between the preview and the product in groups with repeated colors or other SKU values.

What to do after the update:

- Check cards with repeated SKU values and the correspondence of transition images.

- If the site uses a composite cache, update the cache of the affected cards using the site's standard tools.

- The update does not change the grouping rules or images saved in products.

Dubovoi: SKU version 6.4.28

Optimized loading of product variants and their images.

What's new:

- Thumbnails added for product variant images.

What's improved:

- Images of variants outside the visible area are loaded on demand; images of the full list are loaded after it is opened.

- Prices for variants not in the cache are requested in batches while preserving price type availability for user groups.

- Repeated checks of module tables are reduced within a single request.

- Read permissions for related variants and alternative products are verified.

- Names of variants in the standard template remain visible when the image loader is unavailable.

- The full list of the standard template works after a dynamic page update.

Why it is important to update:

- Reduces the number of API calls when cold caching large groups of products and delays loading of hidden images.

What to do after updating:

- Clear the catalog cache and check variant switching, opening the full list, and access rights to products.

- Thumbnails are created on the first access. Ensure sufficient free disk space on the site.

Dubovoi: SKU version 6.4.27

Fixed the product list behavior when selecting multiple smart filter conditions.

What's new:

- The smart filter correctly handles combinations of multiple product characteristics.

- Added the ability to apply a selection rule based on the product's main category.

What has been improved:

- When applying multiple conditions, the product list is no longer limited to SKU group representatives.

- The filter reset functionality and interactive product variant switching have been preserved.

- Clarified the generation of links to product variants and the interactive switching functionality.

- Repeated product changes no longer delay the already scheduled index update.

Why it is important to update:

- Buyers can see all suitable products when selecting multiple characteristics simultaneously.

What to do after updating:

- After updating, clear the catalog cache and verify the section with two or more selected characteristics.

Dubovoi: SKU version 6.4.26

The update preserves module functionality during temporary unavailability of the licensing server for previously issued signed licenses.

What's new:

- A confirmed signed license under the previous scheme continues to permit module operation until its specified expiration date during temporary network errors.

- Strict validation of license date format and calendar correctness has been added.

What has been improved:

- A limited 72-hour backup mode for licenses under the new scheme has been retained.

- License rollback protection and blocking statuses continue to take precedence over the backup mode.

- Visual switching between the "Settings" and "Appearance" tabs has been fixed; the outdated "Catalog Preparation" section is fully disabled in both the interface and handlers.

Why it is important to update:

- The update prevents repeated runtime shutdowns caused by accumulated network errors while a valid signed license under the previous scheme is in effect.

What to do after updating:

- After installation, open the module center and verify that the license is displayed as active.

- No additional manual reset of network error counters is required.

Dubovoi: SKU version 6.4.25

This update resolves erroneous warnings regarding the license and the installation status of the SKU module.

What's new:

- Existing licenses issued prior to the schema verification update continue to function.

- Protection has been added against applying outdated solutions after receiving a newer license status.

What has been improved:

- Verification of the installed module's integrity after a standard update via the Marketplace has been refined.

- Authenticity verification of the update prior to its application has been strengthened.

Why it is important to update:

- The update eliminates false messages about an invalid license signature and erroneous status indicating a modified installation.

What to do after updating:

- After installation, open the module center and click "Check License".

- Ensure that the license is active and the integrity check has completed successfully.

Dubovoi: SKU version 6.4.24

This update adds interactive switching of simple products as SKU without page reload, expands ready-made integrations with Aspro solutions, and increases module reliability.

What's new:

- Added optional interactive switching of simple product variants without a full page reload.

- In the detailed card, the module updates the entire configured product area, synchronizes the URL, page title, and browser history.

- In the listing, the module updates only the selected product card without changing the current page address.

- Added ready-made profiles, templates, and integration examples for desktop and mobile Aspro Max, Lite, and Premier templates.

- Added automatic processing of stuck SKU index rebuild tasks.

- Added a separate documentation page and compact tooltips in the administrative interface.

- Added environment checks and file recovery in case of installation or reinstallation errors.

What's improved:

- The interactive transition is protected by a signed short-lived context, product group membership verification, and a safe fallback to a regular link on any error.

- Strengthened protection for saving rules, settings, and module utility actions.

- Updated control center, rules, index, settings, and integration pages for clearer operation on desktop and mobile screens.

- Improved accessibility of controls and confirmation of potentially costly operations.

- Unified display of SKU parameters and alternative products in supported Aspro templates.

- Strengthened checks for external data, links, HTML, and secure HTTPS connections.

- Expanded automatic checks for installation, uninstallation, queues, public requests, and update builds.

Why it's important to update:

- Buyers can switch product variants faster, while the existing card and listing layout are preserved within explicitly configured update areas.

- The update reduces the risk of the background SKU rebuild stopping after the handler terminates abnormally.

- Administrators receive more accurate statuses, understand the next steps, and have safe error handling during installation.

- Security and compatibility fixes reduce the risk of incorrect data output and issues on current PHP versions.

What to do after the update:

- Install the module update using the standard method.

- Open the SKU index section and verify that the queue is processing automatically without errors.

- If variant changes are needed without reloading, select the integration profile and add the updateable card and listing area boundaries specified in the documentation.

- Check the product card and listing on both desktop and mobile templates after the background queue processing completes.

Dubovoi: SKU version 6.4.23

This update accelerates the loading of SKU switches in the product card when there is a large number of linked variants.

What's new:

- No new user scenarios have been added in this update.

What has been improved:

- Reading of SKU group auxiliary data has been optimized when displaying the product card.

- Database load has been reduced when opening products with a large number of SKU variants.

- Build checks have been updated to ensure the optimization is preserved in future versions of the module.

Why it is important to update:

- The update reduces the risk of slow loading of product cards on large catalogs.

- The fix is especially important for sites with a large number of product variants and an active SKU index.

- The optimization works without rebuilding the SKU snapshot and does not change the switch business logic.

What to do after the update:

- Install the module update.

- No additional rebuild of the SKU index is required.

- After installation, check the speed of opening product cards with a large number of variants.

Dubovoi: SKU version 6.4.22

This update fixes reading SKU properties in the product card if Bitrix returns property codes in a different case or if part of the values did not make it into the snapshot.

What's new:

- No new user scenarios have been added in this update.

What has been improved:

- SKU properties are now matched with rule codes case-insensitively and saved in the snapshot under the original rule codes.

- When assembling SKU data, the module fills in missing values by reading properties via rule codes.

- The product card correctly reads old snapshots where SKU codes were saved in a different case.

Why it is important to update:

- This fix is critical for product cards where numeric or directory-type SKU properties were filled in the products but did not appear in the selectors.

- The update helps display parameters such as width, diameter, or color temperature after rebuilding the SKU index.

What to do after updating:

- Install the module update.

- Rebuild the SKU index for affected rules or wait for the background warm-up so that new snapshots receive the missing properties.

- Clear the product card cache when manually checking a problematic page.

Dubovoi: SKU version 6.4.21

This update fixes the selection of the current index link for SKU in the product card if the product retains old links to previous snapshot groups.

What's new:

- No new user scenarios have been added in this update.

What's improved:

- The product card selects the map link only from the snapshot group where the current product actually exists.

- When saving a snapshot, old map links for these products for the same site, information block, and rule are automatically cleared.

- A scenario has been fixed where some SKU values in the product card could be non-clickable due to selection of an old incomplete group.

Why it is important to update:

- The fix is important for catalogs where products are rebuilt by the background SKU index and may temporarily have multiple links to different snapshot groups.

- The update helps the product card display a complete and current set of SKU variants.

What to do after updating:

- Install the module update.

- Wait for the background SKU group rebuild or run the scheduled rule warm-up so that old map links are cleared when saving fresh snapshots.

- Clear the product card cache when manually checking a problematic page.

Dubovoi: SKU version 6.4.20

This update fixes the selection of the indexed SKU group in the product card when the product already has an active link to a snapshot, but the recalculated scope key points to an old group.

What's new:

- No new user scenarios have been added in this update.

What has been improved:

- The product card now prioritizes the current link between the product and the indexed SKU group.

- Old snapshots that do not contain the current product are no longer used to build SKU parameters.

- SKU diagnostics now include fields showing the source of the index key and the discrepancy between the current link and the recalculated key.

Why it is important to update:

- The fix resolves a situation where extra SKU parameter values could become active in the product card due to reading an outdated snapshot group.

- The update is critical for catalogs with grouping rules based on scope and products that may belong to different sections or be rebuilt by the background indexer.

What to do after updating:

- Install the module update.

- Clear the product card cache or the site-wide cache if you need to immediately verify the fix on a public page.

- In SKU diagnostics, check that INDEX_LOOKUP_SOURCE shows 'map' and INDEX_CURRENT_ELEMENT_IN_SNAPSHOT is true for the problematic product.

Dubovoi: SKU version 6.4.19

This update refines the display of SKU parameters in the product card when some items in the group have empty property values.

What's new:

- Added the "Show single SKU parameter value" setting.

What's improved:

- Empty SKU property values are no longer treated as a separate selection option.

- If the setting is disabled, the SKU parameter is displayed only when there are two or more non-empty values.

- If the setting is enabled, the SKU parameter may be displayed even with a single non-empty value.

- The product card applies the same logic for public SKU assembly and for pre-generated snapshot data in the index.

Why it's important to update:

- The fix eliminates false selection parameters that appeared due to empty values for some items in the group.

- This update is beneficial for catalogs where it is necessary to explicitly display single characteristics of a group, such as diameter or color temperature.

What to do after updating:

- Install the module update.

- If needed, enable the "Show single SKU parameter value" setting on the module settings page.

- Wait for the background SKU index rebuild, or run the scheduled rule warm-up if you need to immediately update the pre-generated snapshot data.

Dubovoi: SKU version 6.4.18

This update fixes SKU grouping in the listing when, according to a rule, there are both ready snapshot groups and new background queue entries simultaneously.

What's new:

- No new user scenarios have been added in this update.

What's improved:

- The listing no longer disables a ready SKU index solely due to the presence of new queue entries for the same rule.

- If a snapshot group is already ready, the section continues to display grouped products, while the queue updates the index in the background.

- The product card and listing now use a single model: ready snapshot data remains available until the background replacement occurs.

Why it is important to update:

- The fix resolves the situation where the product card already sees the SKU group, but the listing temporarily shows products without grouping.

- The update is critical for catalogs with frequent updates from 1C, where the SKU queue may constantly receive new entries.

What to do after the update:

- Install the module update.

- Clear the cache of the section being checked.

- Verify the section with ready snapshot groups and new queue entries: grouping should be preserved, and background processing will continue to update the index.

Dubovoi: SKU version 6.4.17

This update refines the safe operation of the SKU index in listings during background rebuilding and preserves regular products without SKUs in catalog sections.

What's new:

- No new user scenarios have been added in this update.

What's improved:

- Regular products that are not part of SKU groups will no longer disappear from the section when using a ready-made SKU index.

- During active rebuilding, the listing rule temporarily skips the SKU filter and displays the basic catalog output to avoid applying stale cache or incomplete index data.

- The ready-made index preserves SKU grouping but adds regular products in the order of the original section selection, without simply moving them to the end of the list.

- The check for pending rebuilding of the rule is performed without modifying the queue, offset, or agent.

Why it is important to update:

- This update protects catalog sections from the temporary hiding of regular products without SKUs during index rebuilding.

- The fix is especially important for large catalogs where the index may be updated in the background after rule changes or mass product updates.

What to do after updating:

- Install the module update.

- If a background rebuilding is in progress according to SKU rules, wait for the agent to complete processing.

- Clear the cache of the checked section and verify that regular products without SKUs remain in the output, and that after the rebuilding completes, the SKU grouping is restored from the index.

Dubovoi: SKU version 6.4.16

This update fixes the safe reconstruction of the SKU index after changes to rule settings and the group name in the listing.

What's new:

- No new user scenarios have been added in this update.

What has been improved:

- When a rule is resaved without changes to filtering conditions, application areas, or grouping properties, the module no longer immediately deletes working snapshot groups.

- The old index remains accessible on public pages until the background replacement with new snapshot groups is complete.

- A full warm-up of active rules now triggers reconstruction for existing snapshot groups as well, ensuring that saved data, including the group name in the listing, is updated.

Why it is important to update:

- This update prevents a situation where, after resaving a rule, the listing temporarily shows only the already reconstructed groups.

- The fix is particularly important for large catalogs where a full background reconstruction of a rule takes time.

What to do after updating:

- Install the module update.

- On the "SKU Index" page, click "Set active rules" if some snapshot groups were deleted after the previous rule resave.

- Wait for the background queue to be processed by the agent and verify that the snapshot groups for the relevant rule are updating DATE_BUILD / DATE_UPDATE.

- After the index is restored, clear the cache for the relevant section and verify the listing.

Dubovoi: SKU version 6.4.15

This update fixes the processing of SKU group names during index rebuild when the catalog data contains invalid UTF-8 strings.

What's new:

- No new user scenarios have been added in this update.

What's improved:

- The generation of the overall SKU group name is now resilient to invalid bytes in the product name or in the group name property.

- AUTO and PROPERTY_AUTO will no longer move queue records to ERROR due to preg_replace or preg_split errors on strings with invalid encoding.

- The backup reader snapshot also received safe normalization of names to prevent old index data from causing read errors.

Why it's important to update:

- This update is critical for catalogs where data comes from external systems and may contain strings with corrupted encoding in the names.

- The fix allows the background SKU index rebuild to continue instead of stopping individual queue records with a technical error.

What to do after updating:

- Install the module update.

- On the "SKU Index" page, click "Retry Errors" if there are ERROR records remaining in the queue with normalizeListingTitle or common-title processing errors.

- Wait for the background queue processing by the agent and verify that new snapshot groups are created without repeating the error.

Dubovoi: SKU version 6.4.14

This update adds a managed SKU group name in the catalog listing without heavy public data assembly.

What's new:

- Added a group name setting for the listing: do not generate, generate automatically, take from the main product's property, or take from a property with an automatic fallback option.

- The setting can be configured globally in the module parameters or overridden at the level of a specific SKU rule.

- The group name is saved in the SKU index and read by the public listing from a ready snapshot.

What's improved:

- The fast index-hit listing can now return the general group name without reloading the group's products on a public request.

- When the global name setting is changed, the module schedules a background index rebuild.

- When an SKU rule is saved, the rule's snapshot is cleared and marked for rebuild so the new group name is included in the index.

- For the "From main product property" mode, a check has been added: the property must be specified.

- If an automatic name is not found, the module retains the main product's name instead of inserting a random name from the group.

Why it's important to update:

- The update is useful for catalogs where the main product of the group should remain in the listing, but the general SKU group name should be displayed.

- The new logic preserves SKU index performance: the name is prepared in advance and does not trigger heavy runtime assembly on the public page.

- Settings allow flexible selection of the name source for different rules and different catalog sections.

What to do after the update:

- Install the module update.

- In the module settings or in the required SKU rules, select the method for generating the group name in the listing.

- If the property-based mode is selected, specify the code of the main product's property where the group name is stored.

- Wait for the background index rebuild or check the status on the "SKU Index" page.

- After the rebuild, clear the cache for the relevant section and verify the SKU group name in the listing.

Dubovoi: SKU version 6.4.13

This update improves SKU-index performance during mass catalog updates from 1C and migrates the new indexing layer to SKU rules.

What's new:

- A quiet window has been added after mass catalog events: infoblock rebuilding now starts after the change stream completes, not during the export.

- The new SKU-index is now built solely according to SKU rules; legacy UF settings for sections remain for the standard legacy runtime scenario.

What's improved:

- The 1C mass mode is extended while price, stock, and product events continue, preventing constant index rebuilding during the exchange.

- Deferred infoblock rebuilding preserves the offset and continues processing after the quiet window ends.

- The index queue no longer builds legacy groups with RULE_ID=0 and prevents old legacy records from blocking rule-based processing.

- The "SKU Index" page now displays information about the quiet window and the remaining wait time for background processing of mass changes.

Why updating is important:

- This update is critical for stores where 1C performs mass updates of prices, stocks, or products several times a day.

- The index rebuilds in fewer cycles during long exchanges and switches to batch processing once the event stream stabilizes.

- For large catalogs, the new indexing layer becomes more predictable: SKU preparation follows rules without mixing with the legacy UF section model.

What to do after updating:

- Install the module update.

- Open the "SKU Index" page and verify that the queue processing agent is active.

- Ensure that active SKU rules are configured for products that should be included in the new index.

- After the next 1C exchange, check the mass changes block: with an active event stream, it should show a wait for background processing.

- For large catalogs, keep the public runtime SKU assembly disabled and use a warmed-up index based on rules.

Dubovoi: SKU version 6.4.12

This update accelerates the cold loading of the SKU listing when working via the index and reduces the load from outdated snapshot groups.

What's new:

- Added additional protection for the background rebuild of SKU rules: the public listing no longer resets the processing progress of an already scheduled rule.

- Added a database index to accelerate the calculation of the SKU group price range in the listing.

What's improved:

- The catalog listing, when successfully reading the index, now uses a lightweight summary mode without loading items, images, and runtime data for each product in the group.

- Outdated snapshot groups in the listing now schedule a single background rule rebuild instead of queuing each group for a public request.

- The price range in the fast listing mode is calculated via index group rows using aggregated PRICE_MIN and PRICE_MAX.

- Clarified hints for public SKU build settings for large and small catalogs.

- Release checks now verify that the index schema with the new DB index is included in the update package.

Why it's important to update:

- The update is critical for large catalog sections where the first request after cache clearing could generate too many SQL queries even when using the SKU index.

- Public pages participate less in the index rebuild service: updating outdated data is moved to the background process.

- Background rule rebuilds become more stable under active traffic: the processing cursor is no longer reset to the start by public stale-hit requests.

What to do after the update:

- Install the module update.

- Open the "SKU Index" page and ensure the queue processing agent is active.

- For large catalogs, keep the public SKU runtime build disabled and verify that the listing uses an index hit without runtime fallback.

- After the update, clear the cache for the problematic section and re-measure the execution time of the dubovoi:sku_group_section component.

- In large stores, check for the existence of the index ix_dsku_item_group_avail_price in the b_dubovoi_sku_group_item table.

Dubovoi: SKU version 6.4.11

The update reduces the risk of heavy public SKU assembly on large catalogs and accelerates the first grouping calculation in the listing when working via the index.

What's new:

- A "Public SKU Assembly Security" settings block has been added.

- A setting has been added that prohibits heavy SKU assembly on the public page if the index does not provide a ready result.

- A unified policy for public SKU assembly has been added for both the product card and the catalog listing.

What has been improved:

- When reading the index, the catalog listing uses lightweight group data and does not load all group products unless necessary.

- If public SKU assembly is prohibited, the product card and listing set the data for background preparation and do not cache a safe empty result.

- For the listing, the selection of the main group product has been refined: first, the active main product is used, then the active group product, and finally the backup option.

- Mandatory control of the new public SKU assembly policy class has been added to release checks.

Why it is important to update:

- The update is especially important for large catalogs where runtime SKU assembly on the public page can create high load.

- The module receives a managed safe mode: ready data is taken from the index, and unprepared groups are sent for background processing.

- The first listing request after cache clearing should perform fewer heavy operations if a prepared index is available.

What to do after the update:

- Install the module update.

- Open the module settings and check the "Public SKU Assembly Security" block. For large catalogs, it is recommended to keep heavy assembly when no ready index is available turned off.

- Open the "SKU Index" page and ensure that the queue is being processed by the agent.

- After the rules have warmed up, check product cards and sections with a large number of SKU groups.

- If pages were cached, clear the component cache or the Bitrix cache.

Dubovoi: SKU version 6.4.10

A targeted update fixes the saving of SKU rules and restores the display of product images for SKU properties in the card when working via the index.

What's new:

- Added validation of the SKU rule name when saving in the administrative section.

What's improved:

- An SKU rule can no longer be saved without a name: the module displays a clear hint and retains the entered data on the form.

- The functionality of the product_image_props parameter in the product card has been restored when using a ready-made snapshot from the SKU index.

- The product image is once again passed to PRODUCT_IMAGE for SKU properties specified in the product_image_props setting.

Why it is important to update:

- The update prevents loss of entered data when attempting to save a rule without a name.

- The update restores the previous expected behavior of the product card: for selected SKU properties, instead of a text value, a product image may be displayed.

- The fix is important for sites where the product card already uses the new SKU index.

What to do after updating:

- Install the module update.

- Test creating a rule without a name: the rule should not be saved, and the entered data should remain on the form.

- Check the product card where SKU is taken from the index: properties from product_image_props should once again display the product image.

- If the card is cached, clear the component cache or the Bitrix cache.

Dubovoi: SKU version 6.4.9

This update enhances the module for large catalogs: it adds an SKU index, background warming of rules, automatic rebuilding upon catalog changes, and clearer diagnostics for administrators.

What's new:

- A new SKU index contour has been added for product cards and catalog listings.

- An "SKU Index" page has been added to monitor the queue, snapshot groups, product relationships, and background processing status.

- After installing the update, the module automatically sets active SKU rules to primary background warming.

- When creating or modifying an SKU rule, the module automatically schedules a rebuild for that specific rule.

- The index agent temporarily switches to accelerated mode while there is an active queue or a scheduled rebuild.

- Index usage metrics have been added: product cards and listings now show whether fresh snapshots, outdated snapshots, or runtime fallback are being used.

- An index diagnostic log has been added, which can be enabled only during verification.

- A safe fallback has been added: if a snapshot is not yet ready, the public page continues to work via runtime, while the rebuild proceeds in the background.

What has been improved:

- Load on product cards and catalog listings has been reduced for large SKU groupings.

- Rule warming is performed step-by-step and does not load the entire catalog into memory.

- Changing a single rule no longer triggers a full warm-up of all rules.

- During mass changes to products, prices, or stock, the module queues a rebuild and processes it in the background.

- The index queue is less cluttered with empty tasks for products that do not match any active SKU rule.

- Erroneous queue entries can be returned to processing via the "Retry Errors" action.

- Tooltips on the "SKU Index" page have been improved: normal automatic operation is now separated from manual diagnostics.

- HL-blocks for directory properties are now read safely: the module requests only fields that actually exist.

- The module no longer crashes if the directory HL-block lacks a UF_FILE field.

- Image values continue to be displayed for HL-blocks where UF_FILE exists.

- Sorting by UF_SORT continues to work if the UF_SORT field exists in the HL-block.

- Support for the old UF-format is preserved at runtime without forced mass warming.

Why it is important to update:

- The update is especially important for catalogs with a large number of simple products in a single SKU grouping.

- Public pages receive more predictable behavior: ready SKU data is taken from the index, and heavy rebuilding is performed in the background.

- It is easier for the administrator to understand what is happening with the index: how many records are in the queue, whether there are errors, whether snapshot groups have appeared, and whether the site is using the index.

- The transition to the SKU index for active rules is performed automatically after installing the update.

- The update fixes the Bitrix ORM Unknown field definition UF_FILE error on HL-blocks without an image field.

What to do after the update:

- Install the module update.

- Open the "SKU Index" page to monitor the queue status and metrics.

- Wait for the background processing of active SKU rules. Manual warming is usually not required.

- Check the product card and catalog listing for products with large SKU groupings.

- If there is an ERROR in the queue, enable the diagnostic log, fix the cause, and use the "Retry Errors" action.

- For full automatic warming, use SKU rules; old UF-settings continue to work in the previous runtime mode.

Dubovoi: SKU version 6.4.8

The update adds reprocessing of errors in the SKU index queue.

Dubovoi: SKU version 6.4.7

A short technical update of the SKU index.

What's new:

- Fixed processing of the SKU index queue.

What's improved:

- Snapshot building should no longer stop if a price is not found for the product.

Why it is important to update:

- The update is important for stable warming up of the index after creating SKU rules.

What to do after updating:

- Open the "SKU Index" page and check the queue processing.

Dubovoi: SKU version 6.4.6

This update fixes the processing of the SKU index queue for records associated with a specific grouping rule.

What's new:

- The index queue now correctly finds the settings for a specific SKU rule when rebuilding a group.

- The initial record after opening a product card can be processed without a rule search error.

What has been improved:

- Queue processing works more stably after creating a new SKU rule.

- Queue record checks consider the rule, product, information block, and site to assemble the correct group.

- The "SKU Index" page should more clearly show the result of manual queue processing.

Why it is important to update:

- The update is important for the initial warming up of the index after creating an SKU rule.

- The fix is needed so that a NEW record can transition to a processed state during manual or automatic queue execution.

- The package reduces the risk of stopping the initial snapshot group assembly due to a rule determination error.

What to do after updating:

- Open the "SKU Index" page.

- Click "Process Queue" for one test NEW record.

- Verify that the record has transitioned to a completed state or displayed a clear error message.

Dubovoi: SKU version 6.4.5

The update fixes the processing of the SKU index queue and makes errors on the index page understandable for the operator.

What's new:

- AJAX actions on the SKU Index page now return a clear JSON response when processing errors occur.

- Index page buttons are no longer left locked after a request error.

What's improved:

- Queue processing now correctly handles the first card_snapshot_miss: if no links exist yet for the GROUP_KEY, the module attempts to collect a snapshot from the source product.

- When a backend action fails, the operator sees the error text instead of a frozen button and an empty state.

- Queue entries should no longer remain silently in PROCESSING state during a standard rebuild error.

Dubovoi: SKU version 6.4.4

This update makes the SKU index page clearer for working with warming, queues, and snapshot groups.

What's new:

- A separate "Workflow" block has been added to the "SKU Index" page, showing a clear sequence of actions after creating or modifying a rule.

- Button tooltips have been moved to a separate dashed block and are organized by action.

What has been improved:

- Each button on the index page now has its own description: when to use it and what result to expect.

- Instructions are visually separated from parameters and buttons to avoid mixing with working settings.

- Terminology on the page is now closer to operator scenarios: queue, rule warming, snapshot groups, and manual processing.

Why it is important to update:

- The update reduces the risk of incorrect use of the new SKU index contour.

- It is easier for administrators to understand what to do after creating a rule, when the queue is NEW, and when rebuild errors occur.

- This is especially important for large catalogs, where warming and queue processing must be performed step by step and predictably.

What to do after updating:

- Open the "SKU Index" page and review the "Workflow" block.

- After creating or modifying a rule, select it and run "Warm up rule portion".

- Check the "Queue" and "Snapshot groups" tabs to ensure the index has started filling.

Dubovoi: SKU version 6.4.3

The update improves the SKU index page and fixes the registration of the background agent for rebuilding the index.

What's new:

- A clear description of the section's purpose and the procedure for working with the index has been added to the SKU Index page.

- Explanations have been added for the queue, snapshot groups, product relationships, manual processing, and rule warming.

What has been improved:

- Filters on the index page are now hidden by default and open only via a link.

- Long technical group keys no longer break the index table.

- Textual statistics values are now displayed more compactly.

- The background agent for rebuilding the index is now registered with the correct next run date and updates the existing record without creating duplicates.

Why it is important to update:

- The update is important for large catalogs where the SKU index must be rebuilt in the background without placing heavy load on public pages.

- It is easier for administrators to understand what is happening with the queue and when manual processing needs to be started.

- A correctly functioning agent helps the automatic index rebuilding work predictably.

What to do after updating:

- Open the SKU Index page and check the queue status.

- Verify that the SKU index rebuilding agent is active and has the correct next run date.

- After creating or modifying an SKU rule, put the rule through warming and, if necessary, manually process a small portion of the queue.

Dubovoi: SKU version 6.4.2

This update refines the operation of SKU rules and price display in the All Product Variants block.

What's new:

- SKU rules now correctly support filtering conditions by product name, specific products, price, and stock levels without requiring the selection of a grouping property.

- For such rules, grouping is performed by the rule's scope, and selected SKU properties remain only as properties for displaying variants.

What has been improved:

- Conditions based on properties continue to work as before and can form grouping by property values.

- Conditions based on name, price, stock levels, and selected products no longer cause an error regarding empty grouping properties.

- In product card templates, the price in the All Variants block is displayed in its original form without additional replacement of HTML line breaks.

Why it is important to update:

- The update is important for rules where products are combined not by property, but by section scope and additional filtering conditions.

- The product card no longer incorrectly considers such rules incomplete.

- Price display in the variants list becomes closer to the format already prepared by the module or site template.

What to do after updating:

- Check SKU rules where conditions use product name, price, stock level, or a list of products.

- Open the product card and verify that the All Variants block shows the correct variants and price.

- If the index for a rule was already warmed up, set that rule for re-warming.

Dubovoi: SKU version 6.4.1

The update adds a fast SKU index contour for large product groupings and reduces the load on the catalog, product card, and data warming.

What's new:

- A separate SKU Index page has been added to monitor the queue, snapshot groups, product links, and deferred rebuilds.

- A background SKU group rebuild contour has been added for missing and outdated data without heavy synchronous rebuilds on public requests.

- A deferred rebuild mode for information blocks has been added during massive catalog changes, such as after a large export from 1C.

What has been improved:

- Product cards and catalog listings now primarily use the prepared SKU index data.

- SKU rule warming is performed step-by-step and does not load all products of the rule into memory before queuing.

- Lists on the index page use pagination and fast counters to avoid overloading large tables.

- The queue automatically cleans up completed records within the configured retention period.

Why it is important to update:

- The update is especially important for catalogs with a large number of simple products in a single SKU grouping.

- During mass changes to prices, stock levels, or properties, the module should not create heavy loads on public pages.

- Administrators get a clear location to view the index status, processing queue, and deferred rebuilds.

What to do after the update:

- Open the SKU Index page in the module menu and check the queue status.

- Put active SKU rules into background rebuild mode or start warming the required rules using batch jobs.

- After warming, check the product cards and catalog listings for products with large SKU groupings.

Dubovoi: SKU version 6.4.0

The update strengthens the module's security measures and addresses potential vulnerabilities

Mandatory security updates. Potential vulnerabilities have been resolved.

The update improves the operation of stock and price rules for SKU in the card and in the catalog listing.

What changed:

- In rules for the price source and stock source, a mode "As in module settings" has been added;

- If the source is not overridden in the rule, the global module setting is now correctly applied;

- The logic for SKU availability has been fixed: the behavior "Hide / Show without click / Show with click" for zero price and zero stock now works taking into account the selected source;

- Filtering in the listing (sku_group_section) has been improved: the main product in the group is selected only among products that are allowed by availability rules;

- Products that should be hidden or inactive for selection according to rules no longer become "main" in the group.

The update makes the module's behavior predictable when working with warehouses and non-standard price sources, without changing the current integration API.

In this update, the display of prices in the alternative products block has been fixed.

What changed:

- The ruble symbol and other HTML currency entities are now displayed correctly;

- Prices are no longer shown as HTML code;

- The fix applies to the standard template and Aspro solution templates.

This update resolves the price display error in the product card without changing the price calculation logic.

Mandatory update! The module protection system has been updated, and potential vulnerabilities have been eliminated.

Mandatory update! The module protection system has been updated, and potential vulnerabilities have been eliminated.

The logic for grouping products into SKU has been improved in this update.

What this provides:

- You can now flexibly specify which sections to search for products to group;

- The setting can be applied to the entire module at once or individually for each rule;

- The module now more accurately selects products in the product card when working with rules;

- It has become easier to identify reasons why products were not included in the grouping.

This update makes the module's operation more understandable and predictable when configuring different rules for different catalog sections.

Improvements in module operation

Global module update. The module has been transitioned to rule-based management via a rule builder. Product filtering at the section level has been implemented. Module vulnerabilities have been resolved.

The new module version allows:

- configuring product filtering in sections;

- managing SKU grouping from a single interface;

- setting up different scenarios for different catalogs and sections;

- flexibly selecting products for grouping;

- using different SKU parameters in different parts of the catalog;

- separately managing listings, product cards, the "All Options" block, and alternative products;

- using prices from both the catalog and properties;

- accounting for both total and warehouse stock levels;

- smoothly transitioning from the old logic to the new one without losing compatibility.

Before updating, make a backup of the module files or the entire site.

In the new version, the module has adopted a new working principle: instead of rigidly tying logic only to catalog section settings, it now uses a full-fledged product grouping rule system.

This is a key architectural update for the module. Now, an online store administrator can configure grouping behavior not only through section UF fields and general module parameters, but also via a dedicated built-in rule builder within the module interface.

At the same time, an important point: the current working functionality is preserved. If no rules are created, the module continues to operate under the old scheme - via catalog section settings, UF fields, and global parameters. This allows a gradual transition to the new logic without risk to the already configured catalog.

Main version change

The module now features its own product grouping rule builder.

The working logic now follows this priority:

- first, created rules are analyzed;

- if no suitable rules are found, catalog section settings are used;

- if the required logic is still not found, general module settings are applied.

This provides several immediate advantages:

- you can configure different grouping scenarios for different catalogs and sections;

- you can stop reloading UF fields and move management to a convenient interface;

- you can implement new logic selectively without breaking the existing store;

- a centralized control point appears for rules, SKU parameters, listing, the "All Options" block, and alternative products.

What's new in the new version

1. Product grouping rule builder

The module now has a separate page for managing rules.

For each rule, you can set:

- rule activity;

- name;

- priority;

- sorting;

- scope;

- product selection conditions;

- properties for SKU;

- behavior for zero stock and zero prices;

- override of global module parameters;

- settings for the "All Options" block;

- settings for the "Alternative Products" block;

- product filtering settings in the catalog listing.

Rules are stored in the module's own table structure, which allows the system to be developed further without being tied to catalog sections.

Additionally, the module supports working with builder tables: if the tables do not yet exist, the module can detect this and create them via the interface.

2. Flexible rule scope

Previously, logic was mainly defined at the section level. Now, a rule can be applied much more precisely.

Currently, a rule can be linked to:

- a specific site;

- a specific catalog information block;

- one or several sections;

- the entire catalog of the selected information block if no sections are specified.

This allows independent scenarios for different showcases, catalogs, and product groups within a single project.

For example:

- one scenario for footwear;

- another for clothing;

- a separate one for a specific section;

- a separate one for subcategories within a large section.

3. New mechanism for selecting products for grouping

The most important development is the separation of two entities:

- product selection;

- the logic for their subsequent grouping.

Now the module first selects products according to rules, and only then forms SKU groups and selection parameters.

The following selection condition types have been added to the constructor:

- matching property values;

- selecting properties by code prefix;

- selection by product name substring;

- selection by product name prefix;

- selection by specific products;

- selection by positive price;

- selection by positive price from a property;

- selection by total product stock;

- selection by stock levels at specific warehouses.

Conditions can be combined into groups.

The following logic is supported:

- AND;

- OR.

This logic operates at two levels:

- between condition groups;

- within each condition group.

This allows building complex scenarios without code modifications.

For example:

- products from a section that have matching property values;

- or products whose name starts with a specified fragment;

- and at the same time the price must be greater than zero;

- and the product must be in stock.

4. New approach to grouping properties

In the old scheme, grouping properties were specified directly in the catalog section.

In the new version, this development has become more flexible:

- properties involved in selection and grouping logic can now be specified in rules;

- multiple properties can be used simultaneously;

- you can work not only with exact matches but also with property code prefixes;

- this can be combined with other selection conditions.

Strict and non-strict property value checking logic has also been preserved.

This allows solving more complex tasks.

For example:

- grouping products by brand and series;

- grouping by a group of properties with the same prefix;

- considering only products where all required properties are filled;

- or conversely, allowing partially filled properties for more flexible selection.

5. SKU properties are now managed from rules

In the new version, properties that are displayed in the product card as SKU selection parameters can be specified directly in the rule.

This means that different sets of SKU parameters can be used for different sections, catalogs, and scenarios.

The following capabilities have been added:

- quick selection of catalog properties;

- search for properties by name;

- search for properties by symbolic code;

- dynamic loading of suitable properties;

- binding of SKU properties to the selected infoblock rule.

This significantly speeds up configuration and reduces the number of administrator errors when working with the module.

Additionally, the SKU properties block has been made mandatory for the rule to prevent the creation of incomplete configurations.

6. Overriding global parameters at the rule level

Now a rule can not only set product filtering but also override the general module settings for a specific scenario.

This is one of the most important improvements in the new version.

At the level of a specific rule, you can override:

- strict checking for the presence of all property values;

- checking the availability of SKU combinations;

- sorting of SKU values;

- reverse sorting of SKU values;

- excluding products without prices;

- price types without which products are excluded from grouping;

- excluding products with zero stock;

- stock source;

- warehouses for stock checking;

- excluding products by property values.

This provides very precise control over product display logic without the need to create separate custom modifications for each catalog.

7. Configuring behavior for zero price and zero stock

In the new version, the logic for handling unavailable combinations has become significantly more flexible.

You can separately configure behavior for:

- combinations with zero stock;

- combinations with missing or zero price.

For each case, the following options are available:

- hide;

- show without the ability to click;

- show with the ability to click.

Additionally, data source settings have been added:

- price source - trade catalog or property;

- stock source - total stock or stock by warehouses;

- selection of specific price types;

- selection of specific warehouses.

This is especially important for projects where:

- prices are stored not only in the catalog but also in properties;

- stock is tracked per individual warehouses;

- different scenarios must operate under different business rules.

8. The "All Variants" block has become a fully configurable part of the module

The function for rendering the "All Variants" block has now been moved to a separate logical block and received extended settings.

Now you can manage:

- display of the "All Variants" block;

- display of product prices in the block;

- price source;

- price types;

- product name template;

- words that need to be removed from product names.

This allows the "All Variants" block to be used not just as a list of products, but as a configurable selection interface adapted to a specific catalog.

For example:

- remove repeated words from names;

- generate names using a template;

- display only the necessary prices;

- use a price from a property, if the catalog is structured that way.

9. The "Alternative Products" block has become much more flexible

The functionality for alternative products has been significantly expanded.

Now you can manage within rules:

- enabling the block;

- block title;

- depth of search for alternative products;

- depth of subsection nesting;

- hiding products without prices;

- hiding products with zero stock;

- price types involved in filtering;

- price source for filtering;

- properties that must match;

- properties that must differ.

This makes the alternative products block not a static function, but a flexible recommendation tool within the catalog.

Now you can configure alternative products to be:

- products with identical basic characteristics;

- but with a different brand;

- or conversely - with the same brand, but different parameters;

- only from the current section;

- from parent sections;

- from the entire catalog.

10. Product filtering in the catalog listing

A separate major update - development of the grouping component for the catalog listing.

Now, for a rule, you can separately enable or disable product filtering in the listing.

If the option is not enabled, the listing filtering component does not interfere with the catalog operation.

If the option is enabled, the module allows determining which product will be the main one in the group and will remain in the listing.

Supported scenarios:

- main product by minimum price;

- main product by the value of the selected property.

This opens new opportunities for the catalog showcase:

- only one 'main' product from the group can be left in the listing;

- other products will be logically grouped;

- visual cleanliness of the catalog can be managed;

- the cheapest product does not have to be displayed; instead, a product with the required attribute can be shown.

For example:

- main product with the 'new' label;

- main product with the required property value;

- main product with the minimum price.

11. Integration of the component in the catalog listing has been updated

Clear integration rules have been added for the listing.

Now it is separately specified that the listing filtering component must be connected:

- programmatically;

- before calling catalog.section;

- with the same key parameters as used in catalog.section.

This reduces the risk of errors during implementation and makes the module's behavior in the catalog more predictable.

12. A separate 'Module Integration' page has appeared

Integration settings have been moved to a separate page.

This page contains:

- module integration parameters in the product card;

- automatic integration parameters;

- AJAX variant settings;

- examples of component calls;

- hints for connection in various templates;

- explanations for integration in the listing;

- explanations for integration of alternative products.

This is an important improvement for developers and integrators, as logic settings and connection settings are now separated.

13. UX of the rule builder interface has been improved

The interface for working with rules has been significantly redesigned.

Among the improvements:

- highlighting of selected sites and information blocks;

- convenient section selection via popup;

- section tree with search;

- automatic selection of child sections when a parent section is selected;

- more understandable Russian-language formulations instead of technical operators;

- hiding unnecessary parameters if they are not needed in the current context;

- field tooltips;

- grouping settings by semantic blocks;

- hidden additional blocks;

- improved logic for displaying elements AND/OR;

- more intuitive work with importing and exporting rules.

As a result, the constructor has become significantly more convenient for the store administrator and requires less technical expertise for configuration.

14. Import and export of rules

The module now supports transferring rules between sites and projects.

Supported features:

- exporting rules to JSON;

- importing rules from JSON;

- saving existing rules without interfering with already configured logic;

- accelerated transfer of configuration between environments.

This is especially useful:

- when transferring settings from dev to prod;

- when replicating similar stores;

- when deploying the module across multiple projects.

15. Increased reliability and consistency of module operation

As part of the transition to rules, internal module mechanisms have been improved:

- rules now have their own storage schema;

- the logic for determining the active scenario has become prioritized and predictable;

- backward compatibility with the old configuration model has been preserved;

- filter functionality for prices and stock levels has been improved;

- data sources for prices have been expanded;

- alignment of rules and component logic has been enhanced.

This creates a foundation for further module development without accumulating chaotic specific settings.

16. Backward compatibility preserved

This is one of the main advantages of the new version.

The module does not require an immediate abandonment of the old scheme.

If rules are not created, the following continue to work:

- catalog section settings;

- UF fields for sections;

- global module parameters;

- previous integration logic.

This allows:

- implementing the new version without stopping the project;

- transferring settings gradually;

- testing the new logic on individual sections;

- avoiding risks to the already functioning storefront.

What this provides for the store owner and administrator

The new version of the module allows:

- managing SKU grouping from a single interface;

- configuring different scenarios for different catalogs and sections;

- flexibly selecting products for grouping;

- using different SKU parameters in different parts of the catalog;

- separately managing the listing, product card, "All options" block, and alternative products;

- using prices both from the catalog and from properties;

- considering both total and warehouse stock;

- smoothly transitioning from the old logic to the new one without losing compatibility.

Transitioning the module to a rules system is not just a cosmetic interface update, but a full-scale development of the module into a flexible SKU grouping management platform.

The new version makes the module:

- more flexible;

- more scalable;

- more convenient for the administrator;

- more understandable for the integrator;

- more secure for a smooth transition from existing settings.

Minor improvements to the module's operation

Version 1.3.30

- Fixed duplication of the "Also Recommended" block on the Aspro catalog page during AJAX loading of products via "Show More".

- The recommendations block no longer appears in the show-more AJAX response and remains only in the main page render, without breaking the product grid.