razorpay / razorpay-prestashop

Prestashop plugin for Razorpay
12 stars 11 forks source link

Doesn't work with coupon codes and causes 503 #33

Closed hitinder closed 4 years ago

hitinder commented 4 years ago

After I installed it on the Prestashop and tried to add a coupon code at the first checkout step, it caused the website to stop and I ended up getting 503.

Error 503 is only on that particular browser.

Steps to reproduce:

  1. Install the plugin
  2. Enabled authorize and capture
  3. Add item to cart
  4. Apply a promo code
  5. The website will just stop and do nothing and finally end up giving 503

Solution: Clear the cache and delete all browser data and the site will start working.

Version: 2.2.0 Prestashop: 1.7.5.1

ramth05 commented 4 years ago

@hitinder , We just released new version 2.3.0 with the fix for issue listed above. Can you please verify it once in your test site, and please let us know if still some issue.

hitinder commented 4 years ago

@ramth05 If I install the plugin on a subdomain, e.g. test.mywebsite.com. Will your plugin work with the live parameters (keys) without any problem?

ramth05 commented 4 years ago

@ramth05 If I install the plugin on a subdomain, e.g. test.mywebsite.com. Will your plugin work with the live parameters (keys) without any problem?

@hitinder plugin doesn't depend on domain it's only depend on key:secret . So hopefully it should work without any issue.

hitinder commented 4 years ago

@ramth05 it's not working. After applying ore removing the coupon code the payment popup still shows up with the old order value.

Check the popup amount and the amount behind the overlay window.

image

image

ramth05 commented 4 years ago

@ramth05 it's not working. After applying ore removing the coupon code the payment popup still shows up with the old order value.

Check the popup amount and the amount behind the overlay window.

image

image

@hitinder Can you please pass us details of your test or clone site. We need to look issue in your site as unable to replicate it at our end. Before sending us details can you please just remove full installation 'razorpay' folder from modules and clear the cache etc and try to install it again and test it. If it's not working please provide us clone site details to look more into it.

hitinder commented 4 years ago

@ramth05 Working like a charm. It was the cache indeed.

Should I be worried about the below calls taking so much time?

image

ramth05 commented 4 years ago

@ramth05 Working like a charm. It was the cache indeed.

Should I be worried about the below calls taking so much time?

image

@hitinder Thanks for testing it confirming us. I don't think it's related with plugin code. it's must be some time network issue. Please test it throughly before deploying it production. Thanks again for help in testing.

umanghome commented 4 years ago

You don't have to worry about these requests taking time. They are async and non-blocking. Only if one of Razorpay's JS or CSS files were taking time, it would be something to be concerned about.

Thanks for pointing the high response times out - we've raised them to the team.

hitinder commented 4 years ago

@umanghome @ramth05 I flagged them because I believe content like aritel.svg should be marked as static and need not to be loaded for each call. At present this particular SVG file is loading on each call.

hitinder commented 4 years ago

Another thing I noticed is that in the BO it doesn't show RazorPay logo anymore but shows a question mark logo.

image

ramth05 commented 4 years ago

Another thing I noticed is that in the BO it doesn't show RazorPay logo anymore but shows a question mark logo.

image

@hitinder thanks for pointing it, we will check and update it soon.

ramth05 commented 4 years ago

Another thing I noticed is that in the BO it doesn't show RazorPay logo anymore but shows a question mark logo. image

@hitinder thanks for pointing it, we will check and update it soon.

@hitinder just updated the logo in same release razorpay.zip file. We will update new release with this fix soon.

ramth05 commented 4 years ago

Already supported in latest release.