Repository navigation
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
PayPal webhooks are still registered on the plugin's own
/paypal-webhook/api/endpoint, so they never reach the core/payment-methods/{code}notify endpoint added in #814, and the webhook is subscribed to neitherCHECKOUT.ORDER.*norPAYMENT.CAPTURE.REVERSED.The onboarding, the enabler and
sylius-paypal:register-webhook-event-typesnow register the webhook on the notify URL of its payment method, subscribed to every event the plugin handles. Running the command once after the upgrade points a webhook registered on the old URL at the new one through a PATCH, so its id stays the same; the command looks the webhook up straight from PayPal, without the refresh cooldown. The old endpoint keeps working and its controller service is deprecated.