-
Notifications
You must be signed in to change notification settings - Fork 7
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
Thumbnail handling #71
Comments
app/server/helper/media.js line 44 |
From a quick glance, the solution isn't that easy. Since the imagemagick functions are are asynchronous, the So one way would be to get the metadata and do cropping on upload, not on display. |
yes, server side could be very slow and we need to put a lot of code to make this check on every query in node, one single big event in node could have more then 1000 images, nested in different locations Another solution could be a js client side for this very rare case
Some more examples here |
Formats are here, in every item of the sections
|
IMHO we should store the original file on upload and resize it later based on configuration. Resizing during upload solves the performance/async issue, but makes it hard to adjust the layout once different dimensions are required. I'll try to find a solution based on your configs and @alappe suggests and come back here. |
For sure we do it in upload, but this is just for safety reason, noo? |
there was a function that accordingly to the config was lookig for a size format if there wasnt he create it if there isnt the image was taking the default image.
The text was updated successfully, but these errors were encountered: