averixus
Forum Replies Created
-
Thanks for the information, I’ll try
crawl-delay. In the future I would love a feature to apply a rate limit (not just a total block) to a user agent pattern. 🙂Ah of course, thanks!
Thank you so much, replacing the wp-admin and wp-content folders from a fresh install did the trick. Do you have a suggestion for the simplest way to check that emails are sending successfully? (since I don’t have woocommerce or any other plugins which regularly send emails)
I also haven’t received an email despite what the error message says.
Well spotted, thanks. I’ll try the host next.
@mrclayton Which plugin? As I said I don’t have any third party shipping or translation plugins, so I don’t see what else could be possibly be having any effect on this.
@mrclayton I’m referring to the error I mentioned in the first post, here is the screenshot: https://imgur.com/wtwifmS. As I originally said, my shop contains a “rest of the world” shipping option (which is the one selected in the paypal checkout there), so there’s clearly a real problem causing that error to appear.
Hi @mrclayton
I enabled debug mode and had another customer contacting me with an error that same day. This is what they said:
Yes, I refreshed and even cleared the cache, but when I try to pay the page just goes back to the address. The address is still the same, I haven’t changed anything. I’m on my phone right now, but I’ll try again on my laptop later and let you know.
[…]
I managed to pay. When I tried to pay, it showed me two addresses (but actually they were the same). I selected the one I entered manually instead of the suggested one, and it worked.Later than day another customer contacted me to say:
It’s just back to the basket. I can’t go through with PayPal or debit card
I passed on what the first customer had described, and the second customer then got it to work.
I know it’s very challenging to troubleshoot when all we have is secondhand information from non-technical customers! It’s hard to even be sure that what’s being described is actually a single error. But I can safely say I have never had this many customers reporting difficulties with checkout in such a short time, and the first couple of reports included error message screenshots I’d never seen before.
Edit: With that said, most customers are checking out with no issues. So whatever is happening seems to be either intermittent, or only occurs with quite a specific set of circumstances.
- This reply was modified 8 months, 3 weeks ago by averixus.
@mrclayton I was using LiteSpeed Cache (a page cache), but I have just disabled it because it wasn’t adding much functionality. It’s also supposed to automatically exclude the cart and checkout pages so it shouldn’t have had any influence on the error anyway.
The second customer has told me that the error happened after clicking the paypal button, not the card button.
@mrclayton One of the errors was postcode 78257, Texas, USA (that’s the customer who was able to order through the paypal button instead of the card button).
Another was somewhere in the Dumfries & Galloway area of Scotland – I don’t have the customer’s exact postcode but one example postcode in the area is DG1 1NA.
Yes, I assume that’s what they mean because I don’t have any other payment gateways in the checkout.
One of the customers who experienced the error just got back to me with a more detailed description of what happened:
The problem may be the first time I selected credit card and I put in all my info and it still wanted to go through PayPal so I proceeded to PayPal and that when I would get the error code.
After speaking with you, I back tracked and went directly to PayPal without selecting card payment, and thats when it worked.@mrclayton Looks like we posted at almost the same time, but just to confirm: I’m not using any third party shipping or translation plugins. The shipping is set up using the basic woocommerce settings, and includes a “rest of the world” option like I mentioned.
I’ve just looked at the troubleshooting advice from this related thread. (https://ww.wp.xz.cn/support/topic/customer-receive-message-that-shop-is-not-shipping-to-their-address/)
The fatal-errors log file hasn’t been updated since yesterday (both the reported errors happened today, there were no orders yesterday), so there is nothing relevant in there. I don’t use any third party shipping or translation plugins.
Forum: Plugins
In reply to: [W3 Total Cache] 409 errors and reload loop on wp-adminScratch that, it’s not limited to firefox – it started happening in chrome too after a while of using the site. Disabling the plugin resolves the issue so it’s definitely plugin-specific and not a browser problem.