Home New Guten › Forums › WoodMart support forum › Hang on IOS after pressing "back" on browser from payment gateway
Hang on IOS after pressing "back" on browser from payment gateway
- This topic has 9 replies, 2 voices, and was last updated 6 years, 11 months ago by
Artem Temos.
-
AuthorPosts
-
August 27, 2018 at 8:06 am #74431
[email protected]ParticipantHi Support
I have an issue with some script that is running in Woodmart, that is causing a hang if a user clicks back once they have proceeded to the payment gateway.
There is a video of the issue made by the customer, here: https://legwear.co.za/video.mp4
If I look at the issue on another browser, I can see a delay in the following script:
admin-ajax.php?action=woodmart_wishlist_number – it takes up to 3 seconds.Unfortunately there is no dev tools in IOS Chrome nor IOS emulators, so I cannot put a finger on exactly what the issue may be, so am usign the above as an indicator of where the issue might be.
Would it be possible to take a look and see what the issue could be?
Many thanks
CharlesAugust 27, 2018 at 8:34 am #74436
Artem TemosKeymasterHi,
Try to add the following PHP code snippet to the child theme functions.php file to remove this request
function woodmart_header_block_wishlist( $return = false, $is_mobile_menu = false ) { ob_start(); if ( woodmart_woocommerce_installed() && class_exists( 'YITH_WCWL' ) && ( woodmart_get_opt('header_wishlist') == 'header' || $return ) ): ?> <div class="woodmart-wishlist-info-widget"> <a href="<?php echo esc_url(YITH_WCWL()->get_wishlist_url()); ?>"> <span class="wishlist-info-wrap"> <span class="wishlist-label"> <?php esc_html_e( 'Wishlist', 'woodmart' ) ?> </span> </span> </a> </div> <?php endif; $out = ob_get_clean(); if( $return ) return $out; echo $out; }
Regards
August 27, 2018 at 9:16 am #74446
[email protected]ParticipantHi there
thank you – that made no difference so I removed it again.
In further testing, there was another script that appears to have demonstrated the problem:
wc-ajax=update_order_reviewIt was returning a -1, which according to https://docs.woocommerce.com/document/endless-loadingspinner-on-the-checkout-page/ was a cache issue.
Disabling cache in Woodmart fixed the issue.
Thanks
CharlesAugust 27, 2018 at 9:26 am #74447
Artem TemosKeymasterHi,
What WoodMart cache did you disable? There is no any kind of cache option in our theme.
Regards
August 27, 2018 at 9:33 am #74449
[email protected]ParticipantHi
Apologies, wrong term. I disabled minification of JS files. Under performance.
Thanks
CharlesAugust 27, 2018 at 11:15 am #74466
Artem TemosKeymasterStrange, this option should not influence anything there. Do you want us to investigate the problem? In this case, we will need a step by step instruction on how to reproduce it on your website.
August 31, 2018 at 12:41 pm #75050
[email protected]ParticipantHi there
I am afraid I need you to look into this. There was a woocommerce update, and the problem has crept in again.
There is a video of the steps to create – please note this is on IOS only (in Chrome, Safari, on iPhone, iPad, etc) – here: https://legwear.co.za/Video.mp4
Basically the steps to reproduce – checkout with any product, proceed to payment (but dont pay) and go back twice to the checkout screen…
I have re-added the code you supplied above, and still have minification disabled, and this error is not going away.
Many thanks
CharlesAugust 31, 2018 at 12:47 pm #75051
Artem TemosKeymasterHello,
Could you please switch to default WordPress theme and check how it works to understand is it our theme problem or caused by WooCommerce?
Regards
August 31, 2018 at 1:00 pm #75057
[email protected]ParticipantHi
Thank you – not your theme 🙂
Kind regards
CharlesAugust 31, 2018 at 1:02 pm #75058
Artem TemosKeymasterI guess that you don’t need to worry about that. The problem is that when you click on “Back” in the browser it returns you to the checkout page and don’t reload it (on iOS only). That is why it tries to load the data about your previous order with AJAX and can’t do this since the order is already complete. I think that your customers will not face this and hope that WooCommerce will fix it someday. 🙂
Regards
-
AuthorPosts
- You must be logged in to create new topics. Login / Register