Skip to content

Feat: add support for one-page checkout#999

Closed
ThbPS wants to merge 1 commit into
PrestaShop:developfrom
PrestaShopCorp:feat/opc
Closed

Feat: add support for one-page checkout#999
ThbPS wants to merge 1 commit into
PrestaShop:developfrom
PrestaShopCorp:feat/opc

Conversation

@ThbPS
Copy link
Copy Markdown

@ThbPS ThbPS commented May 5, 2026

Questions Answers
Description? Adds support for switching between the classic 4-step checkout and one-page checkout. The checkout navigation is hidden when OPC is enabled, and a hidden toast hook is added for the account-created message after registration.
Type? new feature
BC breaks? no
Deprecations? no
Fixed ticket? N/A
Sponsor company PrestaShop
How to test? Enable one-page checkout, open the checkout page, and verify that the classic step navigation is not displayed. Create an account from checkout and verify that the account-created toast can be displayed after redirect. Then disable one-page checkout and verify that the classic 4-step checkout navigation still appears.

@ps-jarvis
Copy link
Copy Markdown

Hello @ThbPS!

This is your first pull request on hummingbird repository of the PrestaShop project.

Thank you, and welcome to this Open Source community!

Copy link
Copy Markdown
Contributor

@Hlavtox Hlavtox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that there should be a separate template for OPC, this is a recipe for hell.

@ThbPS
Copy link
Copy Markdown
Author

ThbPS commented May 5, 2026

question

@Hlavtox

Since a module cannot cleanly override the theme’s checkout page template, achieving zero OPC dependency in checkout.tpl requires a Core change so that OrderController selects the page template directly.
Or are you suggesting a different approach?

@kpodemski
Copy link
Copy Markdown
Contributor

kpodemski commented May 6, 2026

@ThbPS

In my opinion, the OPC controller can incorporate its own templates/checkout/checkout.tpl and all the needed templates.

This means checkout.tpl would live directly in the OPC module, and you can have all control over the front-office part :)

Alternative option: I'm pretty sure you can extend this template from the module, and correctly use append or maybe even override certain blocks of this page, but, the cleanest way, as mentioned by @Hlavtox is to have a dedicated template, and, to follow my suggestion: directly inside the OPC module.

@ThbPS ThbPS closed this May 21, 2026
@github-project-automation github-project-automation Bot moved this from Ready for review to Closed in PR Dashboard May 21, 2026
@ThbPS ThbPS deleted the feat/opc branch May 21, 2026 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Closed

Development

Successfully merging this pull request may close these issues.

4 participants