Hello,
Our website is running under prestashop 1.6
We encounter a problem since the implementation of the law requiring to apply the VAT of the country of delivery. Indeed, we went from a system where everyone paid the same price to a system where the price depends on the delivery address. For the moment, we do not use a geolocation solution.
Until now, we used a single cache, whether users were logged in or not, using ESI blocks and excluding the whole checkout process. In "Context Vary Bypass" we specified "curr, lang,ctry", with the views being the same for all. This worked well even though we had a huge number of inodes which started to cause problems.
We are now trying to adapt the configuration, but without finding the right combination:
- We removed the "ctry" parameter from "Context Vary Bypass" ;
- We have activated the separate display for visitors and logged in.
Our problem is that for connected users, the price displayed will be the one of the selected shipping country of the first connected person who visits the product/category page.
I was thinking of creating ESI blocks for the prices, but I don't know if this is ok and I'm afraid it will multiply the number of inodes leading to server saturation.
Do you have an idea for a solution? Could a geolocation solution solve this problem, if so which one?
Thanks in advance,
François
Our website is running under prestashop 1.6
We encounter a problem since the implementation of the law requiring to apply the VAT of the country of delivery. Indeed, we went from a system where everyone paid the same price to a system where the price depends on the delivery address. For the moment, we do not use a geolocation solution.
Until now, we used a single cache, whether users were logged in or not, using ESI blocks and excluding the whole checkout process. In "Context Vary Bypass" we specified "curr, lang,ctry", with the views being the same for all. This worked well even though we had a huge number of inodes which started to cause problems.
We are now trying to adapt the configuration, but without finding the right combination:
- We removed the "ctry" parameter from "Context Vary Bypass" ;
- We have activated the separate display for visitors and logged in.
Our problem is that for connected users, the price displayed will be the one of the selected shipping country of the first connected person who visits the product/category page.
I was thinking of creating ESI blocks for the prices, but I don't know if this is ok and I'm afraid it will multiply the number of inodes leading to server saturation.
Do you have an idea for a solution? Could a geolocation solution solve this problem, if so which one?
Thanks in advance,
François