Error in PDF invoice in the VAT detail frame
anndemeyer posted a topic in Bug reportsThere is an error in the invoice PDF when a free product is given (see image). Although the totals are corrert prestahop is not calculating it correctly in the BTW (=VAT)-detail table First of all 6% of 52,66 = 3,16 and not 2,75 And 21% of 10,05 = 2,11 and not 1,29. However 2,11 + 3,16 = 5,17 and not 4,04 The totals on the right part are correct in the PDF: Totaal (Excl btw) = 62,71 Totaal BTW= 4,04 Although if you take the sums of Basisprijs and Totaal BTW on the left part of the pdf they are indeed correct however the individual numbers are not. For accountancy reasons we need to have those right. This is how it should be calculated: There is one shampoo at 13 euro for free so this one should not be taken in the calculation of the totals If we look at the amounts: At 6% VAT 2 x Vanille: 81,13 euro - 20,285 (25% discount) = 60,845 euro 6% VAT = 3,65 at 21% VAT Shampoo 13,00 euro - 13,00 euro (free gift) = 0 euro 21% VAT= 0 Shaker: 2,48 euro - 0,62 euro (25% discount) = 1,86 euro 21% VAT = 0,39 So the left table should look like BTW detail BTW-Tarief Basisprijs Totaal BTW producten 6,000% 60,85€ 3,65€ 21,000% 1,86€ 0,39€ The totals are indeed 62,71€ and 4.04€ VAT I believe prestahop calculates the totals right at the moment the order is placed and stores those totals like that in the database. However the detailed prices and detailed VAT per product is not correct as all the discounts are summed without taken into account if they are a 6% VAT or a 21% VAT discount product.
PS126.96.36.199 WYSIWYG editor disappeared (?)
anndemeyer replied to jura4's topic in Configuring and using PrestaShopI have the same issue after an upgrade from 1.5 to 188.8.131.52. the only error I see in the console in chrome is: Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check http://xhr.spec.whatwg.org/. jquery-1.11.0.min.js:4 Anyone can help?
I have the same issue on a shop I upgraded from 1.5 to 184.108.40.206 The editor is not showing in CMS and products. I have also tried copiing the tiny_mce folder from the original Prestashop files, that didn't help. in Chrome console I see the following error: Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check http://xhr.spec.whatwg.org/. jquery-1.11.0.min.js:4 Any idea how to solve this issue
anndemeyer replied to anndemeyer's topic in OUT - 220.127.116.11 [17 Jun 2014]No, still wailting...
Block layered pagination problem
anndemeyer replied to aur1mielis's topic in OUT - 18.104.22.168 [7 Jan 2015]Hi all, I'm also still having issues with the pagination and layered navigation (v1.11). (prestashop 22.214.171.124) When I click on a categorie, product list appears properly but when I hover over the pagination numbers 2, 3 ... I always see the same url appearing ...livingroom#/page-1. Altough I would expect it to be /page-2, page3 respectively. However when I look at the page source code, I see sometings what seems correct to me: href="/en/5-livingroom?p=2". However when I click on the link the first page is displaying again. It is rather strange as from then on everything seems to work OK when clicking pagination. Unless you select another category. Then it is getting even more strange. The number of products to display are standard to 30 however if I put them to 60. And I select another category. It will only show the first 30 products. Altough the select box displays number 60. The number of pages are also displayed as if 60 products where shown. Again the tooltip of the different numbers also refer to page 1. However when I click on page 2, it goes correctly to the next page. However people have now missed products 31-60. If then you stay in the same category, everthing seems to work normally switching from one page to the other. Here is the link if you want to try it out www.belleetbeau-onlineshop.com Any help is appreciated or should i report this as a bug?