Latest Update Broken
-
The 2.3 version is broken and will not upload images to Amazon S3. Links are placed into WP Media appropriately, but not uploaded to S3.
App 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.
Only displays 4.6% complete when updating metadata.
Can we get the older version?
-
Please add the following to your wp-config.php file.
define('WP_DEBUG', true); define('WP_DEBUG_LOG', true); define('WP_DEBUG_DISPLAY', false);Then hit the “Retry” link in the error notice.
You should get some extra output in
wp-content/debug.logthat might shed some light on the problem.Otherwise, you can always download older versions of WP Offload Media Lite from the bottom of https://ww.wp.xz.cn/plugins/amazon-s3-and-cloudfront/advanced/
Remember, the upgrade is not backwards compatible, so you’ll then need to restore from a database backup.
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 6 years, 3 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:-What does the
amazonS3_inforecord in the postmeta table look like for the record withpost_id= 7996?Also, what its related
_wp_attached_fileand_wp_attachment_metadatavalues?Hi,
there is no
amazonS3_infometa_key forpost_id=7996_wp_attached_fileis2019/12/[email protected]
and_wp_attachment_metadataisa: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 6 years, 2 months ago by
konradg2.
Hi. I have the same issue. Manually retrying upload stop on 99,96%. Issue was discovered a few days ago.
Also, I have only 4 posts with
amazonS3_infometa_value.
a:2: {s:6:"bucket";s:20:"media.youthradio.org.s3.amazonaws.com";s:3:"key";s:66:"wp-content/uploads/2013/11/Joshua-Clayton_Furry-Neighbors_KCBS.mp3";}
for example.My bucket name with length 20 chars but get longer. In my case my bucket
media.youthradio.organd it has length 20 characters. But for some reason, we gotmedia.youthradio.org.s3.amazonaws.comI have resolved my issue. It was related to 4 files with metadata above. That files are from far 2013 and I simply removed them from my server.
Also, I want to note that files actually were uploaded to S3 (I have used links to files in my posts).
When and how something went I don’t know. The plugin used for several years… maybe it was from the very beginning…
Is there any resolution to this?
I have the same issue as the OP.
Except, I only see the “Error Updating Metadata” error if I refresh the page while the metadata is supposed to be updating.
My error log is also full of these errors:
AS3CF: Error saving item: Error saving item:-
And there are no other errors.@domenic95 Do you have an as3cf_items table?
What do your “amazonS3_info” postmeta records look like?
I got same Error on debug.log
[14-Jun-2020 18:10:10 UTC] AS3CF: Error saving item: Error saving item:-Any idea what might be going on?
Thanks!
-
This reply was modified 6 years, 3 months ago by
The topic ‘Latest Update Broken’ is closed to new replies.