Diego Posted November 6, 2018 Share Posted November 6, 2018 My product detail page has a crosselling product carousel, theme developers told me it's based on PS_CROSSELLING so i'm posting this here. The issue, at least for what i could understand by testing, is that it has something to do with the template/cache. Extract of the template code: other.tpl product.tpl pl_grid_layout is set to 1, im sure of this looking at the HTML code + theme setting, so inside product-minature-1 i have this: {block name='product_add_cart'} {include file='catalog/_partials/miniatures/_partials/product-miniature-btn.tpl' nocache} {/block} Looks like that if i leave it like this,everything works fine (see attachments, i can see all the carousel product detail info (title,description,stars). If i remove nocache and i have active cache setting in backend (see screenshots) then only the first product has all the info, the following one has not even generated HTML for those parts. Looking at the compiled smarty file i can say that changing that "nocache" actually change what is generated drastically. Another way to make this work is to simply disable cache in backend setting, but since it's a production webiste with some decent traffic i would like to keep cache enabled and find a solution for this. I couldn't find any way to debug this, enabling debug mode, forcing php to show errors, looking at server log didn't help in any way, Any suggestion/fix for this? Thanks SOFTWARE VERSION: Prestashop: 1.7.4.2 (migrated form an old 1.6.x if it can help understand something with MigrationPro) Theme: warehouse 4.1.7 Link to comment Share on other sites More sharing options...
psg Posted November 8, 2019 Share Posted November 8, 2019 Hello, did you find a solution to this error? Thanks Link to comment Share on other sites More sharing options...
Diego Posted November 11, 2019 Author Share Posted November 11, 2019 Hello @psg, We no longer work for that customer but from what i can remember (this post is 1y old eheh) we didn't find any fix for that, i guess we had to leave that "nocache" in the template inclusion part but we never found the real reason behind that behaviour Hope you have better luck, Cheers Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now