Hello at all,
We would like to integrate a product which can be configured and the chosen options should influence the price.
We have followed your description for an own calculation service (https://docs.coreshop.org/2.0.0/Development/Products/Price_Calculation.html).
We have implemented the CustomPriceCalculator.php in our system as it was descriped in the documentation.
Now we are wondering if the getRetailPrice() function is the best place to integrate additional prices into the calculation?
If so, what would be the best way to pass these values to the function? Additional parameters or could they be included in the context array?
getName
of the Product
, but I don't know if it can work everywhereHi, currently trying to upgrade a Coreshop 2.0 Shop to 2.1 Shop. Didn´t see any BC that are related to my issue:
I´ve overwritten any Controller in the Shop (with V2.0) because the need of much more construct Parameters. Every Controller-Override was defined in the coreshop.yml and of course in the services.yml. Haven´t changed anything. But now i get an errors like this:
Type error: Too few arguments to function AppBundle\CoreShop\Controller\ProductController::__construct(), 0 passed in /cache/dev/getCoreshop_Frontend_Controller_ProductService.php on line 8 and exactly 7 expected
What changes occoured in the frontend Bundle that causes this? Didn´t find any Updates in the docs :-(
Any recommendation how to get fix these issue??
Any idea/suggestion why in my orders, after upgrading to Coreshop 2.1.9 i find in the payment/shipment/Invoice state uncomplete tags?
After i cancel a payment i get back to "revise", and just wondering why "change of payment method is not possible". After a look in the backend i see, there is an incomplete state: "coreshop_workflow_state_coreshop_orderpayment"
Looks like an issue regarding overwriting/extending of the
CoreShop\Component\Order\Transformer\CartToOrderTransformerWorkflowApplier:
decorates: 'CoreShop\Component\Order\Transformer\CartToOrderTransformer'
caused from the "decorates". Create now a new definition in my own yml, and it works again.
{"1":{},"2":{},"3":{},"4":{},"5":{}}
and when I try to import it with {"1":899,"2":769,"3":899,"4":899,"5":899}
the import does not work. Can someone point me to the right formatting?