S3 Upload errors

Hi Venu,

What version of UpdraftPlus is that?

David

It’s Version 1.8.5

I’m using WordPress version 3.7.1 – if that helps.

Hi Venu,

I think it’s going to be tricky to work out from here what the problem is. I suspect that your website has some outgoing proxy which might be interfering. If you’re happy to send me FTP and WP login credentials (to contact at updraftplus dot com) then I can take a look. Or failing that, ask the people running your webserver to take a closer look, or if they won’t do that, ask them if they have an outgoing proxy.

Best wishes,
David

Was any progress made on this? I have the same issue. (running on WebFaction).

I also am having the same issue.

0033.641 (0) PHP event: code E_NOTICE: Undefined property: stdClass::$body (line 2169, wp-content/plugins/updraftplus/includes/S3.php)

The test connection to S3 is fine. Was working in the past just fine.

Hi,

As per the WordPress forum guidelines, please don’t post to resolved threads; see: https://codex.www.ads-software.com/Forum_Welcome#Where_To_Post

If you open a new thread, please indicate what you know, if anything, about any proxies between your web server and the Internet (best is to ask the server admins first).

Best wishes,
David

as per common sense, thread wasn’t resolved.

There is a bug in the code. Hop to that line 2170 and change

else
     $this->response->body .= $data;

to

else
    if (!isset($this->response->body)) $this->response->body =  $data;
    else $this->response->body .= $data;

Hi allengeer,

Thanks. By coincedence, someone else had given me a login on a site with the same issue, and I can confirm that this is the fix. I’ve used this for neatness:

$this->response->body = (empty($this->response->body)) ? $data : $this->response->body.$data;

I’m not yet sure why this problem only appears to trigger on a tiny fraction of sites using Amazon S3; the function is a callback from Curl, so I suspect there’s some subtle race condition involved. But anyway, this does fix it.

Like many plugin authors, we automatically close threads that have had no replies for 2 weeks. Experience shows that many posters won’t close the thread even if they found a resolution to their problem.

David

@david: I apologize for a response again to a resolved thread. Just wanted to give more input because I was one of the people who were having troubles (coincidentally, not with all my sites)

This is indeed a callback from Curl, and that was the issue. I recently moved to a new VPS, and was installing a fresh LAMP stack, and updraft alerted me that my Curl installation wasn’t correct. I cleared this and everything seems to work ok.

So if anyone is having this issue after David applies the fix, make a backup and try to update your Curl installation.