You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There appears to be an issue in spree_chimpy/lib/spree/chimpy/interface/products.rb
I see "invalid ecomm order error" when completing checkout on an order. The MailChimp API serves an error message for the variant image: "Shema describes string, NULL found instead".
This is the rb file snip in question:
I believe line 94 is the issue. When setting the image_url on the product proper, there is some nil checking involved, and the key is excluded if there are no images found for a product.
However, in this case, it looks like variants always include the image_url key which results in passing nil if variant_image_url returns nothing.
Looking at the variant_image_url method (pictured below):
I believe you want to do one of two things:
Add an else condition that returns an empty string
Modify the call to this function and exlude img_url from the Variant object when no images are available
The text was updated successfully, but these errors were encountered:
There appears to be an issue in spree_chimpy/lib/spree/chimpy/interface/products.rb
I see "invalid ecomm order error" when completing checkout on an order. The MailChimp API serves an error message for the variant image: "Shema describes string, NULL found instead".
This is the rb file snip in question:
I believe line 94 is the issue. When setting the
image_url
on the product proper, there is some nil checking involved, and the key is excluded if there are no images found for a product.However, in this case, it looks like variants always include the
image_url
key which results in passingnil
ifvariant_image_url
returns nothing.Looking at the
variant_image_url
method (pictured below):I believe you want to do one of two things:
else
condition that returns an empty stringimg_url
from the Variant object when no images are availableThe text was updated successfully, but these errors were encountered: