-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Image size for Product Watermarks [Magento 2.1.0] #5270
Comments
Hi @RG-1 , thanks for reporting. We've created internal ticket MAGETWO-54779 to fix this issue. Best, |
…#5270 - adding custom validation for AAAxBBB type of inputs in validation rules with translation
…#5270 - modifying js file for simplicity as per code review
…#5270 - modifying js file for simplicity as per code review
…#5270 - fixing error phrase
…#5270 - fixing field for swatches image
Hi guys, |
Hi guys, as this is still not fixed in M2.1.1 there is a temporary solution how to enter the correct "Image Size" in the full format (e.g. 200x300)
and find the following PATH: design/watermark/image_size
|
Hi @RG-1 @gabriel-sf. Please let me inform you this issue was fixed and delivered to the develop branch. The fix was also ported to 2.1 and will be available in one of nearest patches. I'm closing this ticket. Please feel free to reopen if the issue is still reproducible for you on the develop branch. Best, |
Hi @antboiko would you be able to specify how we can implement the patch to fix this issue? |
…'t be set #5270 - applying changes from MAGETWO-54779 to 2.1
…'t be set #5270 - applying changes from MAGETWO-54779 to 2.1
…'t be set #5270 - correcting caps 200X300 to 200x300 for consistency
…'t be set #5270 - modifying regex to support both 200X300 to 200x300
Fixed issue: - MAGETWO-56972: CLONE - [GitHub] Image size for Product Watermarks can't be set #5270
The issue has been delivered to 2.1.3 |
[architecture] ECP-261: Offload Catalog Image Resizing from Magento
Steps to reproduce
Expected result
Actual result
The text was updated successfully, but these errors were encountered: