![]() ![]() Step 5: Go to your store front-office, press Ctrl+Shift+R (or ⌘+shift+R on mac) to refresh your browser cookies. Step 4: Go to your BO -> Advanced Parameters -> and click on Clear Cache button. Step 3: Reset your ps_shoppingcart module from your BO -> Modules. Step 1: Open your core.js file which is inside your themes directory and edit it. PS1.7.7.x, etc) remove it and upload the original core.js file which is within default PrestaShop file (exact the same with your PS version) then follow the rest of instructions. Follow the steps below:īefore I continue to explain the steps, if you have changed your core.js file or you have replaced it with older versions (e.g. Of course thank you to people who posted the core.js patch, which at least help solving the issue.įinally found the solution which works without needing any file replacement or any advanced steps (thanks to our friend response Nawres). Thank you very much Camille I really appreciate your method, finding out the real reason of the issue rather than overwriting a file without knowing the change. I don't know why, but deleting / updating an item now reload the prices cartĪnd that was it ! The e object had only "reason" as an argument. Lucky for me, there was only one "e.resp" in the fileĪfter some console.log and testing, I changed : o. ![]() That was the key to solve the problem, I opened core.js, and searched for "e.resp". JQuery.Deferred exception: can't access property "cart", e.resp is undefined 999/<//themes/core.js So I jumped into the minified core.js and began to console.log.Īfter some time, I noticed in my console that I had a warning (not an error, a warning, and it was hidden at first.): I tried to add a new code.js from the last prestashop version, no change. I am not a fan of downloading a minified JS file from a stranger and to put it on a live website (security first), so I tried to debug it on my own and succeeded. (which doesn't even compile in npm for me □ ) It seems they have done a bit of work on this file (cart.js) since 1.7.7.x so there might be other changes to watch out for as well. Then npm compile this back into your `assets/js/theme.js` should allow you to use the new 1.7.8.x `themes/core.js` without having to make your modification. Make the following changes in `_dev/js/cart.js` (two instances) I then looked into the uncompiled version of `_dev/js/cart.js` from my adapted classic theme (which I also imagine everyone else's themes in this thread are derived from). It has helped me come up with a solution that doesn't involve changing the new `core.js` file.įirst I had a look at the git hub commits for the classic theme and I think the issue we are facing might have been introduced in the following commit ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |