Back office configuration¶
Pagination limits¶
Default pagination limits for different sections of the back office can be defined through respective settings in
ezplatform_default_settings.yaml
You can set the pagination limit for user settings under the ibexa.system.<scope>.pagination_user configuration key:
1 2 3 4 5 | |
You can configure the following settings to manage the pagination limits for the product catalog:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | |
Subtree operations¶
Copy subtree limit¶
Copying large subtrees can cause performance issues, so you can limit the number of content items that can be copied at once by setting the ibexa.system.<scope>.subtree_operations.copy_subtree.limit configuration key.
The default value is 100. You can set it to -1 for no limit, or to 0 to completely disable copying subtrees.
You can copy a subtree by calling the following command in CLI: bin/console ibexa:copy-subtree <sourceLocationId> <targetLocationId>.
Query subtree limit¶
When working with large content trees, counting child items or calculating subtree sizes can cause significant performance degradation due to unbounded database queries.
You can limit these count operations by setting the ibexa.system.<scope>.subtree_operations.query_subtree.limit configuration key:
1 2 3 4 5 6 7 8 | |
The default value for query_subtree.limit is 500.
You can set it to -1 to disable the limit.
This limit is applied when the back office needs to determine if a location has children or calculate the number of items in a subtree. Instead of performing a full count, the query stops after finding the specified number of items, which significantly improves performance on locations with large numbers of children.
Default locations¶
Default location IDs for content structure, Media, and users in the menu are configured with the ibexa.system.<scope>.location_ids configuration key:
1 2 3 4 5 6 7 | |