Ensure BTCPayServer 2.0 compatibility #170
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@deverickapollo could you test the zip attached to this MR? |
BitcoinMitchell
force-pushed
the
fix-btcpayserver-2.0
branch
from
f6cb310
to
7da35b6
Compare
1 task
ndeet
approved these changes
Nov 24, 2024
ndeet
reviewed
Nov 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Replaced the onchain/offchain calls since they seem to be deprecated (without it being mentioned in the API docs). I've removed t he Smarty variant for now.
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Tested locally with Prestashop Kickstarter and the Testnet BTCPayServer instance (which is 2.0.3). Also tested on my own store (which is still using BTCPayServer 1.13.5)
Test Configuration:
Checklist:
Test zip: btcpay v6.3.0.zip