ShopApiPlugin
ShopApiPlugin copied to clipboard
[BUG Report] checkout error
Hi,
I could not make PUT /checkout/{cartid}/address
call after updating my local api server, got a 500 error
Type error: Return value of Sylius\Bundle\CoreBundle\Checkout\CheckoutResolver::getRequestedGraph() must be of the type string, null returned"
have noticed that in v1.0.3 update the checkout_resolve config was removed, but it was suggested for the shop-api server in the readme of this repo, can someone take a look at that, by the way, with this config the put address API call works
my current api server dependencies
- sylius v1.0.3
- syliusShopApiPlugin dev-master
- nelmio/cors-bundle v1.5.3
Hi @sdleiw , I saw the same error when loading the checkout page, it might be the same issue for API. Changing the path matching pattern will resolve the problem, you could check it out from my PR here: https://github.com/Sylius/SyliusShopApiPlugin/pull/246
The same issue with version sylius 1.6.1 and sylius/shop-api-plugin v1.0.0-rc.2 The documentation of this mr helped Although works also with this configuration:
sylius_shop:
checkout_resolver:
pattern: "%sylius.security.shop_regex%/checkout/"
i would sugget reopenning the issue, or updating documentation
The same issue with version sylius 1.6.1 and sylius/shop-api-plugin v1.0.0-rc.2 The documentation of this mr helped Although works also with this configuration:
sylius_shop: checkout_resolver: pattern: "%sylius.security.shop_regex%/checkout/"
I found this config inside of this file config/packages/_sylius.yaml
Thanks.
Is this still an issue in the current configuration? Because now there is no config key like checkout_resolver
in the README
anymore.
Yes, i face this problem and i didn't found any help in README hopefully this topic help me with some research.
This seems to be still an issue.
Can confirm that it still exist.
Adopting the sylius configuration the following way seems to help:
https://github.com/Sylius/ShopApiPlugin/pull/246/files
Why was this removed from the README?
Isn't it related to #647?
@lchrusciel It could the error was something like the graph
is not defined but not sure.
Same problem after adding suggested changes - works