Invoice cancel form backend 404 error

[Syamsg]

Preconditions and environment

• Magento version 2.4.7
• Try to cancel a invoice from backend .

Steps to reproduce

Place an order and create an invoice without capturing payment. After creating the invoice, view the invoice and then attempt to cancel it from the backend.

Expected result

Successfully invoice get cancelled

Actual result

404 error

Additional information

"This error occurred due to commit 3e637056d1031185c7c8989f7a24302cecb5b27b, where Magento\Framework\App\Action\HttpPostActionInterface was implemented for the controller Magento\Sales\Controller\Adminhtml\Order\Invoice\Cancel instead of Magento\Framework\App\Action\HttpGetActionInterface."

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @Syamsg. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this

• To learn more about issue processing workflow, refer to the Code Contributions.

  Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant[bot]]

Hi @engcom-Bravo. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[Syamsg]

Invite me to the slack work space iam not able to join by myself

On Fri, Oct 25, 2024, 12:00 PM m2-assistant[bot] @.***> wrote:

Hi @engcom-Bravo https://github.com/engcom-Bravo. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. ( Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branchDetails- If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
• If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

— Reply to this email directly, view it on GitHub https://github.com/magento/magento2/issues/39299#issuecomment-2436985967, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUQG7AZXFMECH67E3WMQ6WDZ5HQR5AVCNFSM6AAAAABQSSAVC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZWHE4DKOJWG4 . You are receiving this because you were mentioned.Message ID: @.***>

[engcom-Bravo]

Hi @Syamsg,

Thanks for your reporting and collaboration.

Similar issue has been reported here https://github.com/magento/magento2/issues/39298

Hence we are closing this duplicate.

Thanks