Volodymyr

Hello @mateuszgbiorczyk,

Thanks for your reply and help. I’ll investigate it further and will be in touch in case of finding some clue.

I can confirm that warnings are gone after the DB update.

It was caused by removing of wrapping span with wpcf7-form-control-wrap class via my custom php filter.

Fixed now.

• This reply was modified 11 months, 3 weeks ago by Volodymyr.

@mateuszgbiorczyk, thanks for your time too!

I’ll leave it as it is and keep my eye on it. Maybe some clue will come up when content manager will add new products with new photos.

@mateuszgbiorczyk, both steps done and an hour passed after second one – still no errors.

@mateuszgbiorczyk, first step done. I’ll check logs later and report.

@mateuszgbiorczyk, works like a charm. Plugin off – no error.??

@mateuszgbiorczyk, ok, done.

I’ll check logs in a few hours and let you know.

@mateuszgbiorczyk, it is a mystic riddle) I’ve got some files with cyrillic characters in their names thanks to our content manager.

Maybe I should run all files conversion again and show you the output?

@mateuszgbiorczyk, i’ve checked the upload date of latest file in media library: 29.04.2023.

I’ve done a reset of all processes via control panel and a reset of wp cron list via phpMyAdmin.

wp cron task list

The error is still in log.

@mateuszgbiorczyk, for sure. Here they are. As you can see, there only filtered entries of current issue for today.

@mateuszgbiorczyk, sorry for inconvenience, but if you scroll down the page – you’ll find it there.

@mateuszgbiorczyk, some images were not converted because of their dimensions (4000×4000). It was about a month ago. And there were some files with errors at the bottom of Bulk Optimization of Images section in General Settings.

Screenshots of General Settings and Help Center.

@mateuszgbiorczyk, new ones continue to appear.

Hey, @mateuszgbiorczyk!

I’ve switched to default mode and removed certain image types (jpeg, jpg, gif, png, webp) from hosting config panel — and it’s working in normal mode now. It was a server configuration error before.

But the 499 error is still appearing in access logs.

• This reply was modified 1 year, 10 months ago by Volodymyr.
• This reply was modified 1 year, 10 months ago by Volodymyr.