v2.3 not uploading to S3

Using something like the Smush plugin? We’ve seen some problems with their integration with WP Offload Media 2.3.

Otherwise, please add the following to your wp-config.php file.

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

You should get some extra output in wp-content/debug.log that might shed some light on the problem.

No Smush plugin or any other caching or image plugins.

No errors logged or displayed…?like it’s back to default image upload functionality, as if there is no Offload Media plugin.

Media details shows Offload metabox and “not offloaded yet” for new uploads, but never does upload (copy) to S3.

Does v2.3 update require WordPress 5.3?

No, WP5.3 not required.

No notice in WP Offload Media’s settings page about the upgrade routine?

Nope. There had been a notice in WP Offload Media settings after v2.3 update for “Running Metadata Update” but that has since completed, and the new ‘as3cf_items’ table was populated.

New media uploads still do not get offloaded.

I am using version control, so I can revert and also restore database backup and try again, but I don’t think there was an issue during update. Seems the update went as expected, but functionality broken after update.

FYI – I just reverted back to v2.2.1 and restored database backup…
On v2.2.1 functionality is back to expected behavior: add new media, immediately offloaded to S3.

Any code outside of WP Offload Media using one of our as3cf_* filters?

Nothing that I would suspect would interfere.
After update, using WP Offload Media Tweaks, applied the following filters…
'as3cf_update_as3cf_items_table_interval' return 1
'as3cf_update_as3cf_items_table_batch_size' return 1000
'as3cf_update_as3cf_items_table_time_limit' return 50

But same result (new media uploads not offloading to S3) with or without those filters in place.

Similar issue here too. PNG and JPG don’t offload, but a PDF offloaded just fine. No error messages appearing in the window or server log.

I’ve run into the same issue. For me, it appears that the problem is with uploading small files. File sizes less than 150×150 will not cause WordPress to generate resized images, and so then in the amazon cloud front plugin in file:

amazon-s3-and-cloudfront.php

In the method:

wp_update_attachment_metadata

The line that calls this test:

// Protect against updates of partially formed metadata.
if ( wp_attachment_is_image( $post_id ) && empty( $data['sizes'] ) ) {
	return $data;
}

fails because the data sizes is always empty on these smaller files. If I upload a larger file, however, the resize works, and the plugin can correctly upload the file data.

scared

Interesting…?I’ve only tested with smallish .pngs and .jpgs

I have my Media Settings sizes all set to 0 to prevent WP creating all the extra sizes, and also have unset( $sizes['medium_large'] ); which all works properly in v2.2.1.

Wondering if v2.3 relies on WP generated images to function properly?
But glad I’m not alone with offload issue.

After double checking, it looks like the old version of the plugin never enforced this check. To me this looks like a bug, since, as you pointed out @sirschuyler , it is possible to force WordPress to not generate these extra images, which means this check will *always* fail and won’t upload images to your s3 bucket. It looks like there are some funky intermediate things going on during the process of media management, and this extra check was trying to catch it. It just appears to be overly aggressive and missing certain edge cases. Have you look at this @ianmjones ?

Hello – I’m adding my name onto the list. Since updating this plugin to v2.3 it is not uploading to S3. Anything I can do to provide troubleshooting help? I have a very image heavy site and rely on this plugin.

I’m currently running WP v5.3 and Offload Lite v2.3, without issues posting images. PNG files are uploading to S3 as expected. I have this plugin running across several sites, and none have exhibited any issues since the upgrade.

I know this doesn’t help fix the problem. But, sometimes, it helps me to know that it does function in some setups. This might suggest another plugin or configuration with your setup is the cause.

Hope a resolution is discovered soon!

I’m using ShortPixel plugin if that helps at all.