rossdavidh

Just wanted to add for others who may read this thread, that I was having this problem, but uninstalling and re-installing the module did the trick for me. So it's worth trying, even if it doesn't work for everyone it might work for you.

Hi, I've recently gotten a Stripe account and started using the Prestashop Stripe module. I've got it working, in that when I make a purchase it shows up in my Stripe account without a problem. However, it displays this message in Prestashop after the purchase is done: "Sorry, unfortunately an error occured during the transaction. Please double-check your credit card details and try again or feel free to contact us to resolve this issue." Obviously this could be a bit disconcerting for the customer. As I mentioned, there isn't ACTUALLY a problem, the purchase goes through just fine. But, obviously we want to find a way to get the erroneous error message to not appear. I could tweak the CSS to make it not display, but that can't be the best solution. Anybody have any ideas as to what could be causing the non-problem problem? Or maybe even just suggestions on how to debug it? thanks, ross p.s. Prestashop version 1.5.4.0 Stripe module version 0.9.5

Any news on this? I am seeing the same error as Valentin.j, it says the order did not go through. In fact, though, the order does go through, and the money appears in Stripe, but the error message to the user could be worrisome to say the least. My specifics: PrestaShop™ 1.5.4.0 Stripe module Developed by :PrestaShop, Version :0.9.5 Browser: IE 10 or Firefox 22 Five-page checkout, guest account I had IE's developer page (opened via F12) open, but didn't see any Javascript errors Stripe webpage Log shows only "200 POST", which sounds like no error Any ideas for how I could figure out what is causing this error? Anyone besides me and Valentin.j seeing it?

We just performed a similar upgrade, and it appears to only be a problem for items with a Sale price (i.e. discount). For ordinary items (no discount/sale) it shows ok. Is this similar to your situation?

Hello, I've just upgrade our shop to 1.4.7.0. Generally speaking it's gone ok; over time the Prestashop upgrade process has gone from impossible to painful to stressful to pretty good! However, there is one problem I'm having that I've not been able to find a solution for. For some products, we have combinations (e.g. waist size). When we click on the little icon that looks like a pencil and paper, to edit, it says "Choose the reason and enter the quantity that you want to increase or decrease your stock". Which is fine, but there is no button to save your changes. I believe the button used to say "Modify this attribute combination", as per this article on how to change quantity. http://www.ehow.com/...prestashop.html This is how my client remembers it working, but we have no such button now (since the upgrade to 1.4.7.0). The only workaround currently is to delete the existing combination and then create a new one (with the same waist size) with the desired quantity (obviously not what we would prefer). Has anyone seen this, and if so have you found a solution?

Just FYI for others, I had this problem and installing the new gcheckout zip file (see above) solved it.

Don't know Chrome well, but it can happen that at some point a browser has been "zoomed", and remembers to do this whenever you visit that web page specifically. So I'm wondering does it happen with Chrome in other computers (you haven't used before)? Or, if you can find out how (in Chrome) to "reset" you zoom function for this web page. Either way, you would want to make sure it's something all Chrome users would see, or just you.

Just checking, is this change happening for you for all browsers?

I had (I think) a similar problem, and here is how I solved it. Whenever a customer had put something in the cart, but hadn't logged on or entered any address info yet, it would show a very high shipping ($20). This was not what the default shipping method would charge, and it was very frustrating to try to figure out where the problem was coming from. It turns out that it related to how I had broken up USA into many zones (1-8), with different prices (depending on how far they were from our store). Most carriers (in the US) I had selected all 8 zones but had also remembered to UN-select "USA" as a zone. For one shipping carrier only (the expensive one), I had forgotten to uncheck "USA". This, plus the fact that the default country was "USA", meant that when no other information had been entered yet, Prestashop would look for the default carrier for the default country, find that the default carrier was not available for the default country, and therefore look for another carrier that was available for the default country and end up showing the price for the only carrier still available for "USA" (because no state had been entered yet it was not one of the 8 zones). This was the expensive one. Thus, a customer who put a $2 item in the cart would see $20 shipping. If they logged on and entered their address, the shipping would immediately drop to a more reasonable value, but many never got that far. The solution was to make sure that I un-checked the "USA" option for all carriers. Once they enter address info (including state), it shows a sensible shipping price. I don't know if this is relevant to your problem but I offer this info just in case it is.

I have found that this works, most of the time, but (for reasons not yet clear), it doesn't work 100% of the time. We haven't been able to figure out what the cases have in common when it doesn't work.

Sorry for the slow reply. The upgrade process will detect your current version an apply all the SQL for every upgrade between your current version and the new one, so no need to do all the versions in between yourself. On the other hand, it IS very important to follow the advice in the documentation about saving your old version and backing up your database before upgrading. This way, if the upgrade doesn't work as you expect, you can fall back to the old version. Upgrading is a good thing to do (for the security fixes if for no other reason), but it is not uncommon to have problems. So, think through how you will back out the changes (e.g. once you have made a backup of your database, do you know how to restore it?) before upgrading. But, at least you don't have to do it for every version in between your current one and the newest!

That seems to do the trick, thanks very much!

Hello, Is there any way to change the behavior of the shopping cart to not show a Shipping cost until an address and carrier is selected? It really doesn't make any sense to show a shipping cost when you don't know where the recipient is, and depending on the setup it may show a very large shipping cost that will scare off the customer. Once they login/create an account, the shipping cost may be quite reasonable but the default shipping (based on who knows what since it doesn't know the location yet) can scare people away before they ever reach that point. Thanks for any help.

Has anyone here upgraded a website from 1.1 to 1.3.1? On a server running Linux? For a site with 1,000's of items? And had it work correctly? Do you have references to prove it? If so, please contact me ([email protected] or just reply to this post).

Here's an odd idea. Prestashop is, as I recall, fairly easy to install. If they simply had a good export function, it might actually work better to just export everything, make a new install, and then upload your database through the import feature (which is, as I recall, fairly easy to use as well). Maybe I'm just remembering the install as being easier than it was because it's a while ago now, but if there were simply a good CSV export, plus a way to export the pictures, then a clean install and a reimport might be easier than making the upgrade work.