Squashtoppertje

No one really knows what I've done... I'm here to get some thoughts of other people to help me solve this. But I found the problem. It was caused by a module which was loaded in the position displayBackOfficeHeader. After that one was disabled the problem was gone. It's a shame Prestashop is extremely buggy with upgrades.

I'm afraid for the problems that will cause. Shouldn't this work in this version?

Hi, After I upgraded from 1.6.0.9 to 1.6.1.24 I encountered problems in mostly the back office and some on the front end. In the back office things that don't work are (examples): - adding a module because nothing happens when I click "Choose a file" to browse on the hard drive - when configuring a module (for instance Horizontal top menu) clicking on menu-items to add or delete them don't do anything. On the front end in the product list nothing happens when I click on the plus or minus symbol to add or substract the amount or products. It does work on the cart. I have tested it with overrides off and non-prestashop modules off. This didn't help. I do not get an error of any kind. Also not when debug mode is enabled. The only error in console is in help.js and does not look relevant to me: Uncaught TypeError: Cannot read property 'get' of undefined at HTMLDocument.<anonymous> (help.js:69) at j (jquery-1.11.0.min.js:2) at Object.fireWith [as resolveWith] (jquery-1.11.0.min.js:2) at Function.ready (jquery-1.11.0.min.js:2) at HTMLDocument.K (jquery-1.11.0.min.js:2) Any help is much appreciated! Thanks!

Thanks, that's it! Know I can look into the problem.

Hi, After upgrading from 1.6.0.9 to 1.6.1.24 I have an error 500 on the order page. In detail I get the following error: Uncaught Error: Call to undefined method Cart::checkProductsAccess() in /home/..../public_html/testing/controllers/front/OrderController.php:52 Stack trace: #0 /home/...../public_html/testing/classes/controller/Controller.php(170): OrderControllerCore->init() #1 /home/...../public_html/testing/classes/Dispatcher.php(367): ControllerCore->run() #2 /home/...../public_html/testing/index.php(28): DispatcherCore->dispatch() #3 {main} thrown in /home/...../public_html/testing/controllers/front/OrderController.php on line 52 I'm running PHP 7.0, but trying various other versions did not solve this. I can not proceed this way. Any idea how to solve this? Thanks in advance!

Hi, To make some changes I copied a shop (1.6.0.9) to a subdirectory. But somehow when I go to the subdirectory the site does not have the good lay-out and produces a 404. In the code-panel from Chrome I only see it's looking for the wrong cached css (not in test-directory but in the original public_html dir). I've have cleaned the cache, from backoffice AND using FTP. Also I changed the database settings in settings.inc and changed the url in the database in shop_url. Still the system does not recognize the subdirectory to be a websop itself, the system thinks it is a subpage of the original webshop, that's why it produces a 404. BUT WHY????? It is driving me crazy? Any suggestions? Thanks so much!

Thanks good tip, but I want to know how to solve this issue. Any hints where to look?

Hi, I made two changes to the standard template: 1. Added the option to select a certain quantity in the product listing 2. Added the weight in the checkout Both changes work fine, but do produce errors in the logs which I like to solve. In the first case I get the following error: PHP Notice: Undefined index: display_qties in /home/domain.com/tools/smarty/sysplugins/smarty_internal_templatebase.php(157) : eval()'d code on line 385, referer: https://www.domain.com/3-iron PHP Notice: Trying to get property of non-object in /home/domain.com/tools/smarty/sysplugins/smarty_internal_templatebase.php(157) : eval()'d code on line 385, referer: https://www.domain.com/3-iron I think these two errors are part of the same problem. In the second case the error is almost the same, an other variable: PHP Notice: Undefined index: weightUnit How can I solve this? Thanks very much!

Ik heb dit ook: via Chrome tools zie ik een 404 naar www.domein.nl/none. Geen idee echter waar die "none" vandaan komt... Helaas...

Hi there, On the page bankwire/validation I get a blank screen (error 500). In the logs I see a PHP Fatal error: PHP Fatal error: Class 'Swift_Plugin_Decorator_Replacements' not found in /home/.../tools/swift/Swift/Plugin/Decorator.php on line 239, referer: https://www.domain.com/module/bankwire/payment The order can be found in the backoffice, but no email is sent to the buyer. Where should I find this class? It is PS 1.6.0.9. Can somebody pleace help me? I read some other posts about this, but no solutions found (for me). Thanks!

Solved... It took some hours, but it's easy if you know where to look... It had nothing to do with the installation, but with the module European TAX number (or VAT number, I don't know the English name). In the module I once chose a different country for testing. After I selected the right country it was solved.

Hi there, I've got the following issue: In the cart the displayed tax seems to be wrong. In case of B2B customers from my own country, the displayed tax is 0,00%. If a B2B customer is from another country the displayed tax is 21%. But it should be just the other way round. Normally a B2B-customer from the same country as the webshop pays the local tax and B2B customers from other countries do not pay tax in the webshop. So, why is this? How can I solve this? Edit: I was wondering: during installation I had to set a country. I remember I set a different one for testing reasons. This could be the problem, but where is this saved? I can't find it anywhere. Im using PS 1.6.0.9. B2B is enabled. Thanks, Miranda

Nobody?

Hi, I want to show the tax label in the product list also. I have managed to get it on the product page, thanks to this forum, but unfortunately not in the product list. So, below or after the price I want to show: Excl. tax or Incl. tax. How can I get this done? I'm using PS 1.6.0.9. Thanks for your help, Jason

This did the trick for me! Isn't it bizarre however, that this problem exists over two years? Multiple versions and upgrades have been launched since, but they do not bother to solve this? WHile it is such a simple solution. This is one of those things which make me doubt Prestashop. They just don't take their clients seriously. It's a shame, but I won't do any projects with it anymore...