Skip to content

[UPMERGE] 5.1 -> 2026.x - #3271

Merged
dpfaffenbauer merged 3 commits into
2026.xfrom
upmerge/5.1_2026.x
Nov 5, 2026
Merged

dpfaffenbauer merged 3 commits into
2026.xfrom
upmerge/5.1_2026.x

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

This PR has been generated automatically.

Merged automatically. Conflicting Studio build artifacts, if any, were resolved in favour of 2026.x.

Remember! The upmerge should always be merged with using Merge pull request button.

In case of conflicts, please resolve them manually with usign the following commands:

git fetch upstream
gh pr checkout <this-pr-number>
git merge upstream/2026.x -m "Resolve conflicts between 5.1 and 2026.x"

theluckystrike and others added 2 commits October 6, 2026 10:16
reviseAction loaded the payment from the paymentId query parameter into
$payment and then reused $payment as the loop variable over
findForPayable(), which is ordered by id DESC. After the loop $payment
always held the order's oldest payment, so a customer returning from a
cancelled or failed payment saw the note or state message of an earlier
attempt instead of the one that just happened.

Pick the requested payment while iterating over the order's own payments.
This also stops paymentId from loading a payment of a different order.

An unknown order token passed null to findForPayable() and ended in a
TypeError (HTTP 500). Return a 404 instead.

Add a Behat scenario that creates a failed and then a cancelled payment
and checks the revise page shows the cancelled message, plus a scenario
for the unknown token.
…ent-loop

[FrontendBundle] Show the requested payment on the order revise page
@sonarqubecloud

sonarqubecloud Bot commented Oct 9, 2026

Copy link
Copy Markdown

@dpfaffenbauer
dpfaffenbauer merged commit 9dc06a4 into 2026.x Nov 5, 2026
2 checks passed
@dpfaffenbauer
dpfaffenbauer deleted the upmerge/5.1_2026.x branch November 5, 2026 10:15
@github-actions github-actions Bot locked and limited conversation to collaborators Nov 5, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants