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

ProductImageUrls usage in SingleProductViewModel & ImageMagick #513

Open
1 of 4 tasks
alex-pommier opened this issue Dec 13, 2024 · 0 comments
Open
1 of 4 tasks

ProductImageUrls usage in SingleProductViewModel & ImageMagick #513

alex-pommier opened this issue Dec 13, 2024 · 0 comments

Comments

@alex-pommier
Copy link

alex-pommier commented Dec 13, 2024

Sponsorship

If this request requires additional support (e.g., such as direct email/phone/meeting/development), I have the following interest in helping to sponsor the effot via GitHub Sponsors:

  • None, please continute to work for me for free :P
  • Absolutely, I get value out of this!
  • Maybe later
  • I'm already a sponsor... Woot!

Please summarize your question in one sentence

Is "Large Image" MediumUrl in ProductImageUrls? Can we override the default ImageMagick resizing parameters?

Give a more extended description

Using a customized category view the images retrieved by the default SmallUrl are often pixelated and for today's use-cases not adequate. I'm always left using the OriginalUrl because the MediumUrl/LargeUrl is not usable and doesen't retrieve the image. There is also confusion if MediumUrl is the "Large Image" shown on HCC Backend > Catalog > Products > Name, Desc, Price area.

Additionally we've noticed references to ImageMagick and assume that's the library used to resize images on insertion, if we could control the resize parameters this would be ideal somehow via the Admin interface. The default out-of-the box image sizing is always too small for modern sites and causes pixelation on customized views where the category view images are much larger than the default displays. We're always having to switch to the OriginalUrl.

Steps to reproduce (if needed)

N/A

Other comments or remarks

N/A

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

No branches or pull requests

1 participant