[Documentation][Cookbook] How to customize Sylius Checkout? #6538
Conversation
CoderMaggie
commented
Oct 25, 2016
CoderMaggie
commented
| Q | A |
|---|---|
| Doc fix? | no |
| New docs? | yes |
| BC breaks? | no |
| Related tickets | partially #5275 |
| License | MIT |
pjedrzejewski
added
the
Documentation
CoderMaggie
force-pushed
the
docs/cook/checkout
branch
from
c97b38a
to
f35e62c
Compare
| -------------------------------------------- | ||
|
|
||
| This is a common problem for many Sylius users. Sometimes the checkout process we have designed is not suitable for your custom business needs. | ||
| therefore you need to learn how to modify it, when you will need to for example: |
|
Pretty nice for me 👍 But as we've said on today's stand up - we should think about describing some more sophisticated example, as single page checkout, which is quite common use case. |
| Overwrite routing for Checkout | ||
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
|
|
||
| Unfortunately there is no better way - you have to overwrite the whole routing for Checkout. |
There was a problem hiding this comment.
There is a trade-off. We can import Sylius routing and redeclare sylius_shop_checkout_address or paste here whole checkout and remove shipping step. Not sure which way is better
There was a problem hiding this comment.
There was a problem hiding this comment.
After import we would also have sylius_shop_checkout_select_shipping route available and that's wrong. I would say that if we customize checkout it's better to copy the whole routing and have full control over it. Same as we do with the state machine.
There was a problem hiding this comment.
It's even described as best practice http://symfony.com/doc/current/bundles/override.html#routing by Symfony.
CoderMaggie
force-pushed
the
docs/cook/checkout
branch
from
f35e62c
to
662d339
Compare
|
Thank you Magda! :) |
