@javierm24191144 thanks for the question, this topic was pretty good covered in the Developers Live Fireside chat with our product leaders. See https://youtu.be/mSk9bcsVG2s?t=480 (starting at 8:00).
I tried and could not reproduce. The combination AEM 6.5 + Service Pack AEM 6.5.12.0 (I just got the latest) + AEM Commerce Add-On v2022.02.24.00 for AEM 6.5 is working for me. I cannot reproduce the failing bundle starts.
Just "preview" will not work from the editor, since the page requieres the category as context. Without the category information in the URL it will always display the placeholder images.In the action menu of the page editor there is a "Preview with Category" menu item, try this.
This looks like the you used a snapshot version of the Venia reference app, please use a release version: https://github.com/adobe/aem-cif-guides-venia/releases/tag/venia-2021.12.01
The category list in your screenshot has no category information in the URL. With that it always will call back to the placeholder data. There must be category context provided via the URL. What happens if you navigate to a category via the Venia navigation?
The errors you see related to the org.apache.sling.graphql.core.servlet.GraphQLServlet are from CIF and Commerce. This is used by AEM Content Fragment GraphQL.
The category page screenshot form the page editor shows the placeholder data while edition. Try switch to preview and navigate to the category. Or use "View with Category" from the actions menu of the editor.
Hi, this has been changed with the last release, which introduced a switch to use HTTP only as well. However, this is only recommended for local development or demonstrations. Don't disable HTTPS for production environments.
Correct commerce solutions integrated into AEM using CIF do not persist any product data in AEM any more, this is by design.This is not needed any more with CIF as the catalog is driven and controlled by Magento, no need for a shadow catalog in AEM. With the latest release we also support multi temp...