Arnd Zanduino

I did a complete site backup before activating the most recent beta, “v5.5-rc5”. I cleaned up and turned off the cron and turned on debugging.

Unfortunately the error still remains, there are always a few groups/images left on the server for processing (according to the front-end) that never get processed. I’ve checked the debug log for any indications and haven’t seen anything. I’ve logged into the QUIC.cloud to see if there are any messages there, there were none.

I’ve done a couple of manual runs:

200 groups, 828 images, after processing 32 groups with 54 images left.
200 groups, 826 images, after processing 29 groups with 39 images left.
200 groups, 824 images, after processing 31 groups with 47 images left.
200 groups, 827 images, after processing 37 groups with 42 images left.

I neglected to mention that I’d tried changing to another processing node a couple of time in the past, that also made no difference.

Is there a command I can issue to see how many images are actually in the QUIC.Cloud queue?

• This reply was modified 1 year, 5 months ago by Arnd Zanduino.

Yes, I’d be willing to give a beta version a try.

I nuked the database and started again today. The cron settings are turned off for both upload and download.

1. I press “send optimization request” and get notified that 200 groups (800 images) have been submitted.
   06/14/23 11:54:01.386 [147.135.115.64:44840 1 W3I] Images found: 800
06/14/23 11:54:01.402 [147.135.115.64:44840 1 W3I] Images after duplicated: 800
06/14/23 11:54:01.404 [147.135.115.64:44840 1 W3I] Images after invalid: 800
06/14/23 11:54:01.615 [147.135.115.64:44840 1 W3I] Added raw images [total] 800
   
2. After several minutes, I get the following information:

Images requested: 17 groups (31 images)

After the QUIC.cloud Image Optimization server finishes optimization, it will notify your site to pull the optimized images. This process is automatic.

Images notified to pull: 195 groups (551 images)

Since I have the cron job to pull turned off, this display stays constant, even if I wait an hour or wait overnight.

a) 800 images – 31 requested – 551 notified to pull = 218
What has happened to those 218 images? Nothing shows in the debug log.
b) Why do those 17 groups/ 31 images stay forever?
c) When I pull the notified images, then press the “cleanup” and resubmit, the processing starts, I assume, at the first requested image. That means it re-processes images that have already be processed

If I repeat this after “cleanup unprocessed data” then another 200 groups / 800 images are sent and I get

Images requested: 30 groups (42 images)

After the QUIC.cloud Image Optimization server finishes optimization, it will notify your site to pull the optimized images. This process is automatic.

Images notified to pull: 188 groups (518 images)

• This reply was modified 1 year, 5 months ago by Arnd Zanduino.

It seems that the answer is that I should “try it out”. I had hoped for a more definitive answer; I thought that on a site with no personalized pages the original guest-mode page would be identical to the served by the ajax call.

Thanks for getting back to me; but I’m not quite sure if that answer means that using the “guest mode” will give users a quicker and better experience, or if it makes little or no difference. Again, the extra pages in cache and on the server aren’t the issue; it revolves around what the user experiences.

Thanks for the information and links to the source code; I can edit there to make the ordering (and selection) what I’d like.

@benniledl : Will this work with my Astra and Elementor? Looking at the link you sent it seems that the plugin is for Gutenberg blocks.

I had contacted Elementor and they said that this was a known issue and that regenerating their CSS and clearing the cache would solve the problem. It did.