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

sylius_product_variant table data update #1423

Merged
merged 1 commit into from
Apr 23, 2014
Merged

sylius_product_variant table data update #1423

merged 1 commit into from
Apr 23, 2014

Conversation

psyray
Copy link
Contributor

@psyray psyray commented Apr 23, 2014

According to this error

Twig_Error_Runtime: "An exception has been thrown during the rendering of a template ("Could not convert database value "" to Doctrine Type array") in "LVPWebBundle:Frontend/Product:_singleBox.html.twig"

sylius_product_variant table should be updated to fill the missing pricing_calculator and pricing_configuration datas.

This SQL update solve this migration problem for my project.

According to this error

Twig_Error_Runtime: "An exception has been thrown during the rendering of a template ("Could not convert database value "" to Doctrine Type array") in "LVPWebBundle:Frontend/Product:_singleBox.html.twig"

sylius_product_variant table should be updated to fill the missing pricing_calculator and pricing_configuration datas.

This SQL update solve this migration problem
@umpirsky
Copy link
Contributor

👍

pjedrzejewski pushed a commit that referenced this pull request Apr 23, 2014
sylius_product_variant table data update
@pjedrzejewski pjedrzejewski merged commit 7b6df66 into Sylius:master Apr 23, 2014
@pjedrzejewski
Copy link
Member

Thank you @psyray!

@psyray psyray deleted the patch-1 branch April 23, 2014 21:44
@winzou
Copy link
Contributor

winzou commented Apr 24, 2014

@pjedrzejewski This needs to be reverted.
This SQL query needs a brand new migration class, not this one. It does not work as the table sylius_product_variant does not contain column pricing_configuration yet.

@psyray
Copy link
Contributor Author

psyray commented Apr 24, 2014

Hi,

You're right.
Sorry for this mistake.

Fixed with this pull request #1427

Tested and working ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants