Review the following aspects on the e-shop in order to confirm and validate that the default features have been successfully integrated on the Shopware 6 platform.
...
3. Click Enter to load the new URL.
4. If the view stayed the same - there is no API request on the page
| Warning |
|---|
In the case that there is API request on the page and no content loaded - contact the IT team. In the case that there is no API request on the page and it should be - contact the IT team. |
...
This can happen when the theme is not compiled (the integration is a JavaScript update).
The integration team is able to address this directly on the project.
...
If there is no change on the page when inspecting via the _bx_inspect_key - it means the search functionality is not integrated with Boxalino.
The integration team is able to inspect directly on the project:
...
If there is no change on the page when inspecting via the _bx_inspect_key - it means the CMS element is not included in the Category layout or there is a caching issue.
The integration team is able to inspect directly on their project.
...
Review the steps from Search https://boxalino.atlassian.net/wiki/spaces/BPKB/pages/877789187/Testing+the+SW6+Integration#When-there-are-no-products-displayed
When the page is cached
After Shopware 6.4, there is an internal framework layer of cache.
In order to avoid for certain contexts & pages integrated with Boxalino to be cached:
review that the cache invalidator subscribers are part of the integration https://github.com/boxalino/rtux-integration-shopware/blob/3.4.0/src/Resources/config/services/api/cms.xml#L36
update the config shopware.yml.
| Code Block |
|---|
shopware:
cache:
invalidation:
category_route: ["cms-block-navigation-boxalino-api"] |
When the Boxalino CMS Element is not visible
...
The sliders are added on the homepage with the help of the CMS Element CMS Element (for Shopping Experiences) Before continuing with the review, confirm that there the page you are inspect is using an updated layout in use that has a Boxalino CMS Element configured (ex: widget home).
Review the home page with the help of the
_bx_inspect_key=<apiKey>(ex:<e-shop>?_bx_inspect_key=<apiKey>&cacheKey=<some-text>The scrolling events are tracked in the “Network” tab https://boxalino.atlassian.net/wiki/spaces/BPKB/pages/295141377/JS+Tracker+Check-List#Check-the-scrollImpression-tracking%3A
...
If there is no change on the page when inspecting (uncached) via the _bx_inspect_key - it means the :
The CMS element is not included in the homepage layout
...
If the CMS element is included and there is no API request - there is a caching issue and/or some server-side errors.
The integration team is able to inspect directly on the server.
...