Hi there,

If you set 'Photo Image Source Size' to 'Large', it will show large correctly as shown in the 1st screenshot.

If you set 'Photo Image Source Size' to 'Thumbnail', it will show thumbnail correctly as shown in the 2nd screenshot.

The original that you mentioned, do you mean the 'View Original' on the photo dropdown menu? http://take.ms/xhZOV

If yes, what this does is to let you view the original photo in a new tab.

What if I don't allow users "download" images and don't need to keep original images? How to remove it?

I do not really understand what are you trying to bring it up here. Can you provide us with some screenshot so that I can have a better understanding of it?

Hello. When I upload photo, there is 3 files at the server creating:
1) ...thumbnail.jpg
2) ...large.jpg
3) ...original.jpg

May be I’m wrong, but “...large.jpg” and “...original.jpg” has the same size (wight & height).

And I disabled before “view original” and “download photo” options.

So If “...original.jpg” file is not used and I expected that system will not create “...original.jpg” file.

Seems it doesn’t work that’s way?

What will happen if I’ll delete all “...original.jpg” file and never will use “view original” and “download photo” options? It wouldn’t break anything?

Or I should post a feature request: don’t create on Server “...original.jpg” if options “view original” and “download photo” disabled. And if webmaster will turn on this option, system will allow to download “large.jpg” if there is no “...original.jpg” was created before.

Thanks.

Hi there,

Basically all these 3 different image sizes file also needed on the current system, for example :

1. Original - It required this original photo during the rotation of the photo. e.g. http://take.ms/LShVR
2. Large - If those site admin who want to show high quality image, they can decide to show large image source on the site.
3. Thumbnail - If those site admin who want to show low quality image, they can decide to show thumbnail image source on the site.

May be I’m wrong, but “...large.jpg” and “...original.jpg” has the same size (wight & height).

Currently we using PHP GD library to do the resize for the image in Easysocial, it could be this library resize to the same width and height size for certain image, because this is out of our control.

Based on what I tested, if you upload one of the image the dimension is around 1920x1280px, the large size image size will not same with the original image.

By the way, if you would like to reduce some space from your server, what if you can consider to use Amazon S3? Because if your site user keeps uploading those media files like video, image, files and etc on your site, your server space also will not enough to handle it in the future.

And it would help your site backup those media files on the cloud server in case your server sometimes may face some issue, those media files still exist on your cloud server.

Hello. So there is no way at the moment setup system to delete "...original.jpg" files (after uploads) and free disc space usage?

Yes, currently that is not way to remove this.

Hello. I like this new fix:

EasySocial will no longer upscale image sizes when image size is below the threshold
Tuesday, 22 June 2021 13:27 · Modified Files (2) · Removed Files (1)
Modified Files
administrator/components/com_easysocial/includes/image/image.php
administrator/components/com_easysocial/includes/photos/photos.php
Removed Files
administrator/components/com_easysocial/includes/photos/index.html

because usually uploaded image has a low width / height. As result ***_large.jpg and ***_original.jpg are the same (double files on server).

1. Original - It required this original photo during the rotation of the photo. e.g. http://take.ms/LShVR

Hm. Is it possible to edit some core file to make system rotate "***_large.jpg" (not ***_original.jpg)? And may be not to create ***_original.jpg during uploading? Will it works correctly? Thanks.

Unfortunately. there is no simple way to remove this "original" image size variation from the core file because it involved a lot of core files that you need to modify.

Even you can manage to modify to store only large and a thumbnail image size on the site, you also need to think about how to maintain this modification in the future update and this modification is totally changed the default system original behavior, it might create more issue in the future as well.

Or what if most of your site user who requests to download original image for a specific reason in the future? So you can't find back the original image to them anymore.