ndeet
Forum Replies Created
-
Hi, thank you very much for helping debug the issue. I took a slightly different approach than in your fix but it should work same way. Would be great if you could confirm it working for you now with version 2.7.4.
Hey! Thanks for your feedback. As you mention the modalCheckout.js file, it means you still use legacy checkout (not checkout blocks) on your site?
Anyway, I digged a bit deeper into the event handler and it seems that theon()handler does indeed register the same event multiple times and does not deduplicate it likeaddEventListener
Thanks, will test and add to next release.Hey there,
I tried to reproduce but it works for me as expected. When I apply points it creates one order with the discounted price and the BTCPay invoice also has the discounted price. I tried with modal overlay and normal redirect: https://streamable.com/l7v78r (video available for 2 days)
Any more information you can share on how I might be able to reproduce your problem? Are you sure no other plugin (or custom code) is interefering with checkout causing this problem?Hey there,
do I need the Pro version to try to reproduce the problem or does this work with the free version too? It’s the extension from WPSwings, right?
Forum: Plugins
In reply to: [BTCPay Server - Accept Bitcoin payments in WooCommerce] Split PaymentHey there, sorry for the late reply due to holidays.
What you want to achieve is not really possible that way the invoice will always have one destination address and can’t auto-forward on a per invoice basis.
If you only accept Lightning Network payments you can auto-forward by using the Prism plugin, which forwards payments based on LN-addresses. You can find it in BTCPay Server under “manage plugins”.
Normally it would only block until the invoice is generated, so it could be slow if your BTCPay Server is slow with responding. If you generate an invoice in BTCPay itself is it fast?
Anyway, I refactored the legacy checkout to avoid using async:false and also did the same for the new blocks checkout, can you try if it works for you? You can find the file here: https://github.com/btcpayserver/woocommerce-greenfield-plugin/issues/62#issuecomment-3067318250
As it was quite some refactor would be nice if you could confirm it works. Thanks.Hey there, sorry for the late responsue due to holidays.
When you look at the line above that line that disables async behaviour it says:
> // We need to make sure the order processing worked before returning from this function.
This means there was some problem with the async behaviour and the order was not created for some reason. Maybe this has long been fixed in WooCommerce and this workaround is not needed anymore. I will do some tests and see if we can remove that part.Forum: Plugins
In reply to: [BTCPay Server - Accept Bitcoin payments in WooCommerce] Avast allertingMaybe checking your site with https://sitecheck.sucuri.net/ helps. It does not detect anything on my site where the plugin is enabled.
Forum: Plugins
In reply to: [BTCPay Server - Accept Bitcoin payments in WooCommerce] Avast allertingHi, that’s strange never heard of it but I also don’t use Avast. Does it maybe show any more details when you click on the error?
I have found a few false positive threads like this one, caused by WP Rocket and others https://community.avast.com/t/false-positive-site-blocked-html-script-inf/771646/9
Not sure what the process is to get it unflagged, seems people are running a bit in circles there.Ok then you need to log into the server and check the logs there, more troubleshooting tips here:
https://docs.btcpayserver.org/TroubleshootingHi, as you mentioned this is an error on the BTCPay Server side and not the plugin itself. On BTCPay go to “Server Settings -> Logs” and check what error you get there.
Hi, thanks for the feedback.
The qr not showing up for 5-10 sec is more likely due to slow response from your BTCPay Server but I agree that redundant requests should not be done. Care to share your fix or do a pull request here https://github.com/btcpayserver/woocommerce-greenfield-plugin ?
Hi, this plugin works only in combination with WooCommerce. If there is a shortcode for embedding WooCommerce checkouts, then yes you can use it that way.
It sounds like you want to trigger your make.com stuff only after the payment has been completed and not when the order is created to ensure make.com only gets triggered in that case.
How does your current setup look like? You trigger make.com stuff with a webhook from Woo or BTCPay? Maybe there is a Woo make.com plugin that fixes your issue?
Right, there is no country specific reporting but a generic report that you can download via CSV. It is impossible to cover all countries reporting structures. But there should be tools that allow you import the relevant data into such a 1099-K report.