Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account container rendered twice on checkout success page #4999

roma84 opened this issue Jun 13, 2016 · 3 comments


Copy link

@roma84 roma84 commented Jun 13, 2016

Steps to reproduce

  1. Install Magento from develop branch.
  2. Enable and configure Paypal Express and billing agreements.
  3. Sign in.
  4. Add Product to cart.
  5. Go to checkout.
  6. Select Paypal.
  7. Check Billing Agreement checkbox.
  8. You will be redirected to success page after payment completed.

Expected result

  1. Billing agreement number rendered in page content

Actual result

  1. Billing agreement number rendered twice: in page content and page bottom.
  2. Screenshot:

Possible solution

in app/code/Magento/Checkout/view/frontend/layout/checkout_onepage_success.xml move inside checkout.success block:

<referenceContainer name="content">
    <block class="Magento\Checkout\Block\Onepage\Success" name="checkout.success" template="success.phtml" cacheable="false">
        <container name="" label="Order Success Additional Info"/>
Copy link

@ishakhsuvarov ishakhsuvarov commented Jun 14, 2016

@roma84 Thank you for reporting this issue. We have created an internal ticket MAGETWO-54380 to fix the problem.

Copy link

@qbo-tech qbo-tech commented Jan 10, 2017

Confirmed issue on 2.1.3....

Copy link

@magento-engcom-team magento-engcom-team commented Sep 20, 2017

@roma84, thank you for your report.
The issue is already fixed in 2.2.0

magento-cicd2 pushed a commit that referenced this issue Jan 28, 2020
[TSG] Fixes for 2.2 (pr121) (2.2.11-develop)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants