ndeet
Forum Replies Created
-
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.
Hi, not sure what you mean. Inside BTCPay Server you have a reporting section where you can export payment data for accounting. For overall revenue reports inside WooCommerce I would search for plugins that do that, there have to be some.
Forum: Plugins
In reply to: [BTCPay Server - Accept Bitcoin payments in WooCommerce] BTCPay Server URLHi, great that you solved the issue.
This could happen if you enter your domain but the DNS has not been propagated yet and the request fails for that reason, or if there is a typo or the https missing.
Hi @edwinoonk the latest release 2.6.1 allows you to disable the notification forever. Hope this will solve your frustration and make you reconsider your rating.
Hi @hansderuiter, you can still use version 2.5.0 which does not have that requirement https://github.com/btcpayserver/woocommerce-greenfield-plugin/releases/tag/v2.5.0
With 2.6.0 I upgraded the BTCPay PHP library that is used and the library has PHP 8.0 as minimum requirement, that’s why and because PHP 7.4 is EOL for very long time the min PHP version was updated to PHP 8.0.Hey, glad you made it work. You could still use 2.5.0 which supports PHP 7.4. No security updates had been done and if there were we could release a 2.5.x version although unlikely for the following reasons:
Even PHP 8.0 is end of life and does not get any security updates anymore since Nov. 2023. PHP 7.4 since Nov 2022. Security updates for PHP 8.1 will end Nov 2024. This means we supported 7.4 for more than 1 year even after it’s official end of life.
Btw. your claim that removing support for PHP 7.4 makes this in any way “insecure” is nonsense. It is insecure to keep running unmaintained PHP versions.If you click on the X on the top right it should not appear for 30 days, or otherwise there is a bug. But I will make a “dismiss forever” link in the next release so it won’t show up again if that is clicked.
This is a free and open source plugin and complete bitcoin payment solution and we do not make any money. Reminding users every 30 days to give us a review when they are happy so we have a better ranking sounds like a fair deal. It is not like other commercial plugins that want to sell you something permanently. Your one star review just for this is disappointing. Hope you reconsider or uninstall our plugin and use another solution.
Hi @kalprajsolutions this has now been fixed in v2.4.1. Thank you for your patience.
Hi,
it is a bit strange that you have two expired events changing the order status once it fired 4:15pm when it added the note of an expired but partially paid invoice. After that you manually changed the order status. On 4:47pm there was another “Invoice expired” event but this time without a partial payment.
It seems like the second expired event was caused by a new invoice attached to the same order, so what could have happend is that the customer tried a second checkout with his cart? Otherwhise I can’t explain how there would be a second entry for the expiry.
Sounds like this would not be a common thing to happen, right?
That said, yes I could add an option to protect order status changes once the order status is “processing” or “complete”.I added a ticket here for you to track: https://github.com/btcpayserver/woocommerce-greenfield-plugin/issues/31
Hi, thanks for reporting back. The event of changing the payment method afaik only fires when one is actually selected but maybe there is a case why it still triggers on ajax requests. Please test with the latest plugin version 2.2.2 which should have fixed the issue by exiting the function if there is no payment method selected.
Hi Christian,
users can use the browser back button to change their mind. To have a button on the BTCPay invoice/checkout page you can bring it up (or search if there is a similar request already there) to see if more people would need that feature https://github.com/btcpayserver/btcpayserver/discussions- This reply was modified 3 years, 9 months ago by ndeet.
Hi Antonin,
yes you need to set the custom message on the payment gateway itself because if you save it once it will not use the fallback to the default from (global) settings anymore. Great you found out yourself.
- This reply was modified 4 years ago by ndeet.