konradg2

Hello @crossi72,

many thanks – your workaround works well – I intentionally removed files from local upload dir and it downloaded them from AWS S3 and renamed.

Unfortunatelly I can’t fully test it so far, because ShortPixel blocks some operations (it has problems with our configuration as well :)) and I can’t disable it on production server. Your fix was very handy – it will help us in making this all works better and we continue to use it – that’s for sure.

Thank you once again for quick replies and for your help with sorting this out ??

Have a great day!
Konrad

Thanks a lot @crossi72, sure I will test it and let you know in the begining of next week ??

• This reply was modified 4 years, 7 months ago by konradg2.

Thanks @crossi72 for you reply – that would be great.

Meanwhile tested it on configuration with WP Media Offload but not behind load balancer (so copy of files are always there in uploads folder). It works good with this configuration with no visible drawbacks – image is renamed in both local uploads folder and on AWS S3.

I wonder if solution would be to detect that file is offloaded, download it to local uploads folder and then rename (the rest of this process seems to work fine).

Regards,
Konrad

Hi,

there is no amazonS3_info meta_key for post_id=7996

_wp_attached_file is 2019/12/[email protected]
and _wp_attachment_metadata is

a:5:{s:5:"width";i:772;s:6:"height";i:1000;s:4:"file";s:17:"2019/12/[email protected]";s:5:"sizes";a:7:{s:9:"thumbnail";a:4:{s:4:"file";s:17:"[email protected]";s:5:"width";i:150;s:6:"height";i:150;s:9:"mime-type";s:9:"image/png";}s:6:"medium";a:4:{s:4:"file";s:17:"[email protected]";s:5:"width";i:232;s:6:"height";i:300;s:9:"mime-type";s:9:"image/png";}s:12:"medium_large";a:4:{s:4:"file";s:17:"[email protected]";s:5:"width";i:768;s:6:"height";i:995;s:9:"mime-type";s:9:"image/png";}s:23:"tournament_tile-full_hd";a:4:{s:4:"file";s:18:"[email protected]";s:5:"width";i:772;s:6:"height";i:1000;s:9:"mime-type";s:9:"image/png";}s:23:"tournament_logo-full_hd";a:4:{s:4:"file";s:17:"[email protected]";s:5:"width";i:496;s:6:"height";i:466;s:9:"mime-type";s:9:"image/png";}s:14:"banner-full_hd";a:4:{s:4:"file";s:17:"[email protected]";s:5:"width";i:772;s:6:"height";i:510;s:9:"mime-type";s:9:"image/png";}s:14:"avatar-full_hd";a:4:{s:4:"file";s:17:"[email protected]";s:5:"width";i:140;s:6:"height";i:140;s:9:"mime-type";s:9:"image/png";}}s:10:"image_meta";a:12:{s:8:"aperture";s:1:"0";s:6:"credit";s:0:"";s:6:"camera";s:0:"";s:7:"caption";s:0:"";s:17:"created_timestamp";s:1:"0";s:9:"copyright";s:0:"";s:12:"focal_length";s:1:"0";s:3:"iso";s:1:"0";s:13:"shutter_speed";s:1:"0";s:5:"title";s:0:"";s:11:"orientation";s:1:"0";s:8:"keywords";a:0:{}}}

• This reply was modified 4 years, 12 months ago by konradg2.

Update: manually retrying worked up to 94% and stopped working – now it’s always 94% and error log is full of these:
[29-Feb-2020 16:37:43 UTC] AS3CF: Error saving item: Error saving item:-

Hello,

I have exact same problem. It run once, then after refreshing in 2 minutes it says

Error Updating Metadata — We ran into some errors attempting to update the metadata for all your Media Library items that have been offloaded. Please check your error log for details. (#8) Try To Run It Again

When cron job is run there is error debug.log:

[29-Feb-2020 09:30:35 UTC] AS3CF: Could not construct item for attachment with ID 7996 from legacy offload metadata.

and cronjob gets removed from cron job list.

No such error when running “Try To Run It Again” from wp-admin. It get’s about ~1% per each manual run.

• This reply was modified 5 years ago by konradg2.