Content model data provider¶
The content model data provider provides an implementation for fetching catalogs and products from the database.
Products are stored directly in the content structure. They can use the features provided by the content model such as languages, Objects states, versioning, etc. The product catalog can be maintained in the Back Office.
The data provider uses configuration to limit the fetched catalog elements.
The following default setup filters content of type
ses_category for the navigation service
(which uses this data provider to fetch the category objects).
The sort order is controlled by the Priority field and the publish date.
The second level key defines the scope, or
filterType, for which the specific filter definitions are valid.
In this example, the
navigation is passed by the navigation service's fetch.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
If a product has multiple Locations, the shop ensures that the proper Location is returned, so the URL of the product is correct.
By default, hidden items (e.g. products) are not fetched.
||Identifier of the Content Types defined in the system|
||Default limit to be used when no limit is given|