Image Optimizer for XF 2.0

Image Optimizer for XF 2.0 [Paid] 3.0.1

No permission to buy ($29.00)
So I just did some testing and I get something weird going on.

I tried to compress this image:

It's 2.8 MB originally.

If I download the image from the postbit after compression, I still get 2.8 MB:


but the log in XF's admincp says otherwise (and yes, it's 100% the same image since it's a test zone with just myself there):

1665556652487.png


What am I missing?
 
What you downloaded is a cache HIT from Cloudflare. I assume you force cache attachments on the Cloudflare side.
This is a disadvantage of the addon running on cron, as there is usually a few minute delay in optimizing the image after the file is uploaded.
 
So I just did some testing and I get something weird going on.

I tried to compress this image:

It's 2.8 MB originally.

If I download the image from the postbit after compression, I still get 2.8 MB:


but the log in XF's admincp says otherwise (and yes, it's 100% the same image since it's a test zone with just myself there):

View attachment 274851


What am I missing?

Login to Cloudflare and clear everything from cache. Go back to optimised image. Right-click the image and open in new tab. CTRL+F5 to force refresh. Is the newly loaded image the optimised (smaller) one?
 
Please, can you help me? This problem - when I click Verify button. (chmod for this file is settings)

io.webp
 
You need to enter the path to the binaries, not the scripts. For example:
/usr/bin/pngquant
/usr/bin/jpegoptim
/home/nginx/domains/mydomain.com/public/src/addons/Truonglv/ImageOptimizer/gifsicle
 
Hello! I have pre-sales questions before buying an addon.
1. Is this addon changes attachments IDs?
2. Does it changes location/paths? After addon working does attachments stay where it was before (folders/paths)?
3. Main question (summing up above) does addon overwrite images? or changes to new ones smaller size?
 
Last edited:
Hello! I have pre-sales questions before buying an addon.
1. Is this addon changes attachments IDs?
2. Does it changes location/paths? After addon working does attachments stay where it was before (folders/paths)?
3. Main question (summing up above) does addon overwrite images? or changes to new ones smaller size?
1. No
2. The attachment will stored in same folder with origin.
3. Override the origin.
 
I was really hoping that was an option. I don't need high-res images in the chit chat like forums on the site.

It’s not about resolution of the images - it’s about reducing the file size on disk of all posted images (whilst retaining the size/resolution); which should be good for your site as a whole. (y)
 
It’s not about resolution of the images - it’s about reducing the file size on disk of all posted images (whilst retaining the size/resolution); which should be good for your site as a whole. (y)
I agree to an extent ... If I have a forum for photographers sharing print quality images, I don't want those optimized. Or if I'm future planning and don't want a forums images optimized because 5yrs down the road maybe we have 800 dPI screens or something ...
 
I agree to an extent ... If I have a forum for photographers sharing print quality images, I don't want those optimized. Or if I'm future planning and don't want a forums images optimized because 5yrs down the road maybe we have 800 dPI screens or something ...

Personally, we didn't notice any degradation in image quality. We did have that concern, initially, so did some small-number test runs to compare the before and after images, and at least for our purposes, the quality remained high.
 
Personally, we didn't notice any degradation in image quality. We did have that concern, initially, so did some small-number test runs to compare the before and after images, and at least for our purposes, the quality remained high.
Hello. What quality did you set? 80 by default?
 
You should be okay to let it run in the default batch process. It's worked it's way through just over 200k attachments, albeit not very compressed...

View attachment 265613
I think you might have a problem with your binary paths. I am testing this on a local server and had the same problem it didn't compress anything. I then tried a new installation of the binarys and fixing the paths and after that it started working.
 
Back
Top Bottom