-
Notifications
You must be signed in to change notification settings - Fork 754
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
Non-Integer Thumbnail Sizes Break API Calls #5291
Comments
I will submit a PR |
I am pretty sure this commit introduces a new url requirement for the profilepic mode. If you do not include the maxHeight or maxWidth (which I don't think is currently happening by default) the DefaultDimension of 10px becomes the maxHeight and maxWidth. This makes some renderings blurry and defaults others to small sizes. It could impact themes and modules that use the ImageHandler as well upon the next upgrade. If there are no additional concerns regarding the maxHeight and maxWidth params then it may be less disruptive to bypass the DefaultDimension implementations for requests made for profilepic mode. Here is a branch I can submit as a PR that tries to fix this or it may just be referenced on the way to something more robust. |
…dnnsoftware#5292) * DNN-61848 - Core Engineering Maintenance * Update DefaultDimension to be 10 px Co-authored-by: Ricardo Tejo <ricardo.tejo@trilogy.com>
@DNNMonster I agree this is a breaking change, can you submit that as a pull request |
Description of bug
Non-Integer Thumbnail Sizes Break API Calls
Steps to reproduce
It is easy to reproduce the failed API calls with non-integer parameters: make an API call to http://{your dnn install}.dnndev.me/DnnImageHandler.ashx?mode=securefile&fileId={a file id}&MaxWidth=74.98&MaxHeight=42.01
Current behavior
API calls return with HTTP 500
Expected behavior
API parses the non-integer parameters and returns thumbnail based on rounded dimensions
Screenshots
See here https://docs.google.com/document/d/1DgWvWwNloNGleA7zpt6sqb4fT_W1V9gSwzmZhRBWKBg/edit
Error information
n/a
Additional context
n/a
Affected version
Affected browser
The text was updated successfully, but these errors were encountered: