szmigieldesign

In my opinion this setting should be a global switch. Either all files are stripped from metadata or all have them. There’s no need for EXIF in thumbnails, but colour profiles are much needed.

For example, prior to optimization I had an issue with photography.szmigieldesign.pl where originals opened in lightbox had sRGB attached to them and they displayed correctly. However, images in slider were technically thumbnails and they were stripped from colour profiles which resulted in colour shift. One could see oversaturated image at first and had different original in lightbox.

I had to install a WP plugin that forces image conversion through imagick that retains metadata to counter this effect.

This problem doesn’t occur in Chrome as it falls back to sRGB when no profiles are found. However, Firefox saturates the hell out of images if there’s no profile attached. It can be changed in about:config, but it’s non-standard.

One problem that I see is that WordPress by default strips metadata from thumbnails if the processing isn’t done with external tool like imagick. So, for most users the option to retain metadata will apply only to originals anyway.

FYI – I’ve tested it on one image. I’ve regenerated thumbnails for it and whole operation was transparent for LSCache. It treats all images as optimized.

It would be nice to have at last a “Force Reoptimize” feature and ideally – rescan option (I don’t know – maybe MD5 or size based) that would mark for optimization not whole groups but only thumbnails that had changes in size.

It might be useful also in context of upcoming update that doesn’t strip metadata from optimized images (like – how am I supposed to reprocess already processed images?).

Do you have any workaround suggestion for this? What if WordPress introduces another size and won’t delete any old ones – will LSCache interpret new thumbnails as never processed and mark them for processing?

Yup. It finally pulls them and it seems that the pull is initialized correctly with cron.

12/05/17 16:06:13.732 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] GET HTTP/1.1 /wp-admin/admin.php
12/05/17 16:06:13.732 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] Query String: page=lscache-optimization&type=img_pull&LSCWP_CTRL=media&LSCWP_NONCE=1efb78f7b0
12/05/17 16:06:13.732 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] Cookie _lscache_vary: admin_bar:1;logged-in:1;role:99
12/05/17 16:06:13.819 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] X Cache_control -> private ( logged in user )
12/05/17 16:06:13.819 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] LSCWP_CTRL: media
12/05/17 16:06:13.819 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] LSCWP_CTRL verified: 'media'
12/05/17 16:06:13.819 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] Router parsed type: img_pull
12/05/17 16:06:13.820 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] Media: Manually running Cron pull_optimized_img
12/05/17 16:06:13.870 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] IAPI posting to : https://eu.wp.api.litespeedtech.com/client_pull
12/05/17 16:06:14.257 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] IAPI failed to decode post json: "took too many times"
12/05/17 16:06:14.257 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] Media: Failed to pull optimized img: --- '"took too many times"'
12/05/17 16:06:14.257 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] 301 from https://photography.szmigieldesign.pl/wp-admin/admin.php
12/05/17 16:06:14.258 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] 301 to https://photography.szmigieldesign.pl/wp-admin/admin.php?page=lscache-optimization&type=img_pull
12/05/17 16:06:14.258 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] X Cache_control -> no Cache ( 301 to same url )
12/05/17 16:06:14.258 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] not cacheable before ctrl finalize
12/05/17 16:06:14.258 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] X-LiteSpeed-Cache-Control: no-cache
12/05/17 16:06:14.258 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] Optimizer bypass: Not frontend HTML type
12/05/17 16:06:14.258 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] End response
--------------------------------------------------------------------------------

12/05/17 16:06:14.347 [2a02:a317:e141:8600:5dad:816a:3588:6917:20673 1 xrC] GET HTTP/1.1 /wp-admin/admin.php
12/05/17 16:06:14.347 [2a02:a317:e141:8600:5dad:816a:3588:6917:20673 1 xrC] Query String: page=lscache-optimization&type=img_pull
12/05/17 16:06:14.347 [2a02:a317:e141:8600:5dad:816a:3588:6917:20673 1 xrC] Cookie _lscache_vary: admin_bar:1;logged-in:1;role:99
12/05/17 16:06:14.453 [2a02:a317:e141:8600:5dad:816a:3588:6917:20673 1 xrC] X Cache_control -> private ( logged in user )
12/05/17 16:06:14.521 [2a02:a317:e141:8600:5dad:816a:3588:6917:20673 1 xrC] X Cache_control -> no Cache ( Admin page )
12/05/17 16:06:14.623 [2a02:a317:e141:8600:5dad:816a:3588:6917:20673 1 xrC] not cacheable before ctrl finalize
12/05/17 16:06:14.623 [2a02:a317:e141:8600:5dad:816a:3588:6917:20673 1 xrC] X-LiteSpeed-Cache-Control: no-cache
12/05/17 16:06:14.624 [2a02:a317:e141:8600:5dad:816a:3588:6917:20673 1 xrC] Optimizer bypass: Not frontend HTML type
12/05/17 16:06:14.624 [2a02:a317:e141:8600:5dad:816a:3588:6917:20673 1 xrC] End response
--------------------------------------------------------------------------------

It doesn’t pull the images. I’ve clicked it. There’s a cron job running for 15 minutes every 15 minutes on my server and images won’t pull. Spamming wp-cron.php doesn’t help either.

I’ve clicked both – with no effect on pull.

Right now, clicking “Send Optimization Request” does nothing (no confirmation or error).

Are you getting any errors on your side? Can I produce some extra debug info? I’m happy to help.

This is what I see now:
Image

I no longer get an error when trying to push more images to process but it still doesn’t pull them back. I’m stuck with 94 notified and 73 optimized and pulled. Images failed to fetch is still 10.

Hello,

unfortunately still no go. This time:

` Failed to push to LiteSpeed server: “Too many errors while fetching image source files for previous request.” ‘

After I click Send Optimization Request.

Requesting the pull with the new Pull Images button seems to initiate the pull as the timer increases whenever I click Update Reduction Status but it doesn’t pull anything. Spamming wp_cron.php doesn’t help either. It’s locked on 93 notified and 73 optimized and pulled.

I’ve submitted the report if it’s helpful:

Report number: CCGMCXJU
Report date: 11/30/2017 22:43:47

• This reply was modified 7 years ago by szmigieldesign.

Unfortunately still no luck.

Failed to push to LiteSpeed server: Previous requests that optimized but not pulled: 8178

My other sites on the same host work flawlessly and they all have default wp-cron disabled and it’s invoked with crontab every 15 minutes.

Awesome. Will I have to reprocess my images after this feature is implemented?

Resolved.

Hosting fixed timeouts.

I’ve contacted my hosting company and they’ve replied that this functionality is being implemented and I’ll be informed on their progress. I hope that’ll fix the errors as this plugin’s image compression implementation is one of the best among WordPress plugins – good quality, good speed gains.

This is what I have on photography.szmigieldesign.pl now:

Erorr:
Failed to push to LiteSpeed server: Previous optimization requests remaining in queue: 1183

Stats:
Images total: 480
Images not yet requested: 380

Waiting to be pulled: 27
Optimized and pulled: 73