Merged
Conversation
mnocon
commented
Mar 31, 2026
mnocon
commented
Mar 31, 2026
ibexa-workflow-automation-1
bot
requested review from
adriendupuis,
dabrt and
julitafalcondusza
adriendupuis
requested changes
Apr 3, 2026
Contributor
There was a problem hiding this comment.
month_change: true missing in several pages.
When moving from local to Quable:
- Can I use the local and the Quable PIM at the same time?
- How do I handle purchases without carts and orders?
- What happens to taxonomy tree(s) precisely?
- What are the product search criteria and sort clauses I'll have to stop using?
Some old pages could mention Quable
- Product catalog configuration could mention
quableas another possible value fortype. - Product search references could indicate what is supported by Quable.
Comment on lines
+2
to
+3
| description: Quable PIM connector configuration reference for Ibexa DXP | ||
| page_type: reference |
Contributor
There was a problem hiding this comment.
Suggested change
| description: Quable PIM connector configuration reference for Ibexa DXP | |
| page_type: reference | |
| description: Quable PIM connector configuration reference for Ibexa DXP | |
| page_type: reference | |
| month_change: true |
| @@ -0,0 +1,170 @@ | |||
| --- | |||
| description: Install and configure Quable PIM connector for Ibexa DXP | |||
Contributor
There was a problem hiding this comment.
Suggested change
| description: Install and configure Quable PIM connector for Ibexa DXP | |
| description: Install and configure Quable PIM connector for Ibexa DXP | |
| month_change: true |
Comment on lines
+2
to
+3
| description: Quable PIM integration with Ibexa DXP | ||
| page_type: landing_page |
Contributor
There was a problem hiding this comment.
Suggested change
| description: Quable PIM integration with Ibexa DXP | |
| page_type: landing_page | |
| description: Quable PIM integration with Ibexa DXP | |
| page_type: landing_page | |
| month_change: true |
Comment on lines
+2
to
+3
| description: The Quable product guide describes how you can use the product data from Quable in Ibexa DXP to create marketing campaigns built around your products. | ||
| month_change: false |
Contributor
There was a problem hiding this comment.
Suggested change
| description: The Quable product guide describes how you can use the product data from Quable in Ibexa DXP to create marketing campaigns built around your products. | |
| month_change: false | |
| description: The Quable product guide describes how you can use the product data from Quable in Ibexa DXP to create marketing campaigns built around your products. | |
| month_change: true |
Contributor
There was a problem hiding this comment.
There is probably more missing month_change: truethan those abvious ones.
|
|
||
| You can use [[= product_name =]] to manage product availability and pricing for [[= pim_product_name =]]'s products, including creating advanced pricing strategies with [discounts](discounts.md) combined with [regions](product_catalog_guide.md#regions) and [currencies](product_catalog_guide.md#currencies). | ||
|
|
||
| ## Known limitations |
Contributor
There was a problem hiding this comment.
I feel like this isn't the place for this section as it get a bit too technical and detailed for a guide. But I see know better place.
As limitation to the capabilities, I would "hide" it a bit under this section.
Suggested change
| ## Known limitations | |
| ### Known limitations |
Or even move it down after Use cases?
Contributor
Author
There was a problem hiding this comment.
Moved down after use cases 👍
Comment on lines
+64
to
+67
| |[ProductName](productname_sort_clause.md)|Product's name| | ||
|
|
||
|
|
||
| ### Manage stock and pricing |
Contributor
There was a problem hiding this comment.
Suggested change
| |[ProductName](productname_sort_clause.md)|Product's name| | |
| ### Manage stock and pricing | |
| |[ProductName](productname_sort_clause.md)|Product's name| | |
| ### Manage stock and pricing |
Comment on lines
+2
to
+3
| description: Ibexa DXP provides product catalog capabilities for managing products, product types, variants, attributes, pricing, and catalogs. | ||
| page_type: landing_page |
Contributor
There was a problem hiding this comment.
This introduction to the total revamp of what was PIM (https://doc.ibexa.co/en/5.0/pim/pim/) worth being labeled as new.
Suggested change
| description: Ibexa DXP provides product catalog capabilities for managing products, product types, variants, attributes, pricing, and catalogs. | |
| page_type: landing_page | |
| description: Ibexa DXP provides product catalog capabilities for managing products, product types, variants, attributes, pricing, and catalogs. | |
| page_type: landing_page | |
| month_change: true |
I like this new https://ez-systems-developer-documentation--3085.com.readthedocs.build/en/3085/product_catalog/product_catalog/ by the way.
dabrt
requested changes
Apr 13, 2026
| ### `ibexa_format_product_attribute` | ||
|
|
||
| The `ibexa_format_product_attribute` filter formats the attribute value to a readable, translated form. | ||
| Rendering is performed using a configurable list of Twig templates with named blocks. |
Contributor
There was a problem hiding this comment.
Suggested change
| Rendering is performed using a configurable list of Twig templates with named blocks. | |
| Rendering is performed by using a configurable list of Twig templates with named blocks. |
"Rendering is performed by using a configurable list of templates..." or rather "Rendering is performed by using templates from a configurable list..." ?
Contributor
Author
There was a problem hiding this comment.
Changed to:
Rendering is performed by using Twig templates with named blocks, defined in a configurable list.
| <li><a href="pim/catalogs/">Catalogs</a></li> | ||
| <li><a href="pim/prices/">Prices</a></li> | ||
| <li><a href="product_catalog/product_catalog_configuration/">Product catalog configuration</a></li> | ||
| <li><a href="product_catalog/quable_integration/">Quable PIM Integration</a></li> |
Contributor
There was a problem hiding this comment.
Suggested change
| <li><a href="product_catalog/quable_integration/">Quable PIM Integration</a></li> | |
| <li><a href="product_catalog/quable_integration/">Quable PIM Integration add-on</a></li> |
Will we add Raptor to the index page as well?
Contributor
Author
There was a problem hiding this comment.
Let's discuss this after the release - it's a good idea
Co-authored-by: Tomasz Dąbrowski <64841871+dabrt@users.noreply.github.com>
katarzynazawada
approved these changes
Apr 14, 2026
Co-authored-by: Tomasz Dąbrowski <64841871+dabrt@users.noreply.github.com>
Co-authored-by: Tomasz Dąbrowski <64841871+dabrt@users.noreply.github.com>
Co-authored-by: Tomasz Dąbrowski <64841871+dabrt@users.noreply.github.com>
Steveb-p
approved these changes
Apr 14, 2026
| | `webhook_secret` | string | Secret expected in the [webhook](https://docs.quable.com/v5-EN/docs/webhook) authorization header. | | ||
| | <nobr>`throw_on_invalid_criteria`</nobr> | <nobr>`%kernel.debug%`</nobr> | Controls behavior for unsupported search criteria: `true` throws an exception, `false` only logs unsupported criteria. | | ||
| | <nobr>`throw_on_invalid_mapping`</nobr> | <nobr>`%kernel.debug%`</nobr> | Controls behavior for mapping errors during data transformation: `true` throws an exception, `false` only logs mapping errors. | | ||
| | `cache.enabled` | `true` | Global cache switch for the connector. When set to `false`, cache decorators use only [in-memory cache](persistence_cache.md#in-memory-cache-configuration). | |
Contributor
There was a problem hiding this comment.
Suggested change
| | `cache.enabled` | `true` | Global cache switch for the connector. When set to `false`, cache decorators use only [in-memory cache](persistence_cache.md#in-memory-cache-configuration). | | |
| | `cache.enabled` | `true` | Global cache switch for the connector. When set to `false`, only [in-memory cache](persistence_cache.md#in-memory-cache-configuration) is used. | |
Also, I'd like to note that we are using cache.app.taggable (so indirectly cache.app) to create caching services, which means we are using the cache that is declared for Symfony framework. See https://symfony.com/doc/current/cache.html#system-cache-and-application-cache
cache.appis a general-purpose data cache for application and bundle code. Data in this pool does not need to be flushed on deployment. It defaults tocache.adapter.filesystem, but configuring a faster adapter like Redis is recommended when available (this ensures cached data survives deployments and is shared across multiple instances in a multi-server setup).
Contributor
Author
There was a problem hiding this comment.
Added as:
When set to
true, [Symfony'scache.appcache pool]([[= symfony_doc =]]/cache.html#system-cache-and-application-cache) is used.
linking to https://symfony.com/doc/current/cache.html#system-cache-and-application-cache
| product_type_group_identifier: product | ||
| ``` | ||
|
|
||
| This configuration defines two engines: the default `local` engine and the new `quable` engine, allowing you to work with products defined within [[= pim_product_name =]]. |
Contributor
There was a problem hiding this comment.
Siteaccess cannot use both at the same time. Two repositories would be needed. It is one-or-the-other.
| - [Catalogs](product_catalog_guide.md#catalogs) can't be created from [[= pim_product_name =]] products. | ||
| - Product assets are not fully synchronized. Only the main asset thumbnail URL from [[= pim_product_name =]] is used. | ||
| - [Product-level access restrictions](policies.md#products) based on product type are not supported. | ||
| - Products with unsupported identifiers (containing `/` or exceeding 64 characters) are not synchronized. |
Contributor
There was a problem hiding this comment.
That's not exactly true.
If product contains / or it's identifier is longer than 64 characters, then certain "attachments" (availability, price management) won't work for it due to our arbitrary limitations (which might / are likely to be changed in upcoming versions).
Suggested change
| - Products with unsupported identifiers (containing `/` or exceeding 64 characters) are not synchronized. |
Contributor
Author
There was a problem hiding this comment.
Changed to:
- You can't define prices and availability for products with product codes exceeding 64 characters.
As discussed on Slack
dabrt
approved these changes
Apr 14, 2026
7 tasks
Co-authored-by: Paweł Niedzielski <pawel.tadeusz.niedzielski@gmail.com>
* Added doc for language configuration * Apply suggestion from @mnocon
|
code_samples/ change report
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation for the upcoming Quable connector.
Most important changes:
ibexa_quable_instance_url