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
{{ message }}
This repository has been archived by the owner on Apr 17, 2020. It is now read-only.
I try to display a large image when opening a product page.
I configured the iéage settngs style attribute in the addim interface but still when opening the product page in front end, i can see no way to display a large or even original size picture of the product. the largest displayed have is the small one inside the circle, so no way to figured the product in details
According to documentation setting the style to large shoudl solve that...or there is something i did not catched
Thanks
The text was updated successfully, but these errors were encountered:
Comprehensive list of steps to reproduce the issue.
Add a large image to a product. it uploas fine, paperclip creates the 4 sized images correctly. But there is no way to display the large image a product page. we only can see the image product inside the circle
I reproduced that on the demo store .
the product is . http://majestic-store-5639.spree.mx/products/apache-baseball-jersey
What you're expecting to happen compared with what's actually happening.
To click on the image or on a link to display the the product image in large format
The version of Spree and the version of Rails.
spree is edge one
Rails is 4.1.3
ruby is 2.1.0
I try to display a large image when opening a product page.
I configured the iéage settngs style attribute in the addim interface but still when opening the product page in front end, i can see no way to display a large or even original size picture of the product. the largest displayed have is the small one inside the circle, so no way to figured the product in details
According to documentation setting the style to large shoudl solve that...or there is something i did not catched
Thanks
The text was updated successfully, but these errors were encountered: