Hoodgrown Posted June 9, 2009 Share Posted June 9, 2009 For all the trouble i went to get shipping modules.. my new dropshipper uses table based rates so I had to delete my previous UPS module.I've set up the rates and made a default carrier but now I get a "hack attempt" when I try to add stuff to the cart.I had seen the solution to this on the forum before... but now that I'm searching for it.. I can't seem to find it...can u help? Link to comment Share on other sites More sharing options...
Hoodgrown Posted June 9, 2009 Author Share Posted June 9, 2009 found the answer to this... Re: Hack Attempt ErrorUtterly maddening error. Anyways, this happens when you have an active cart and then change shipping options while the cart is active. What happens is Prestashop seems to save the cart forever and the old shipping id that was linked to it. So every time you load a page that deals with the cart, the site dies and you get the Hack Attempt Error. Note this is pretty much every page because most people have the cart plugin enabled for their sites.Solution: Go into your database – most likely phpmyadmin – you need to find the _cart table. It will have a prefix in front of it that was chosen when you installed, so it could be something like ps_cart or similar. Delete the last few entries in this table. That will delete the cart that is giving you the error and allow you to re-enter your site.I hope that helps. I was getting real tinkered for a little bit. And don’t change shipping methods for your shop while you are logged into the front end of your site. Make sure your cart is always empty before messing with shipping options. Link to comment Share on other sites More sharing options...
bovill Posted August 7, 2009 Share Posted August 7, 2009 Hi Hoodgrown or anyone.Can you please be a bit more specific with this:"It will have a prefix in front of it that was chosen when you installed, so it could be something like ps_cart or similar. Delete the last few entries in this table. That will delete the cart that is giving you the error and allow you to re-enter your site."I can find the table with my _cart info but i don't want to be deleting the wrong things, i am having this same problem and yes it was from mucking around with shipping stuff and countries while being logged into the front end and now my site is broken, can someone please urgently help?Thanks much appreciated. Link to comment Share on other sites More sharing options...
TWFree Posted March 2, 2013 Share Posted March 2, 2013 (edited) The above recommendation - to delete 'the last few entries' which are shopping carts, is sketchy. It is yet another community hack for prestashop and might not even work. It is a very lame recommendation because it is 'hand waving' at the problem, does not describe the actual cause of the problem, and warns us not to be logged into the frontend while changing things in the backend, but doesn't explain why or even what will happen if we do that. I suppose at least I know shopping might be up with specific carts to cause the problem? Any such behavior which is described generally as: being logged into the frontend and not being able to perform an activity on the backend is a bug. This report probably has nothing to do with getting hacked, more likely yet another fatal bug! Edited March 2, 2013 by TWFree (see edit history) Link to comment Share on other sites More sharing options...
Dh42 Posted March 3, 2013 Share Posted March 3, 2013 This is a 3 year old topic, why are you rehashing it? Link to comment Share on other sites More sharing options...
TWFree Posted March 3, 2013 Share Posted March 3, 2013 (edited) Sorry but it's frustrating to see such inaccuracies and poor advice. The issue is cited here from Nov 2012: http://forge.prestas...owse/PSCFV-5905 The patch was committed 7 weeks ago here: https://github.com/P...lasses/Cart.php Thank you for your help. Edited March 3, 2013 by TWFree (see edit history) Link to comment Share on other sites More sharing options...
Dh42 Posted March 3, 2013 Share Posted March 3, 2013 The version numbers on those issues are different from the version in this thread. Link to comment Share on other sites More sharing options...
.png.022b5452a8f28f552bc9430097a16da2.png)
Recommended Posts