azega

What I understand as the difference between 1.7.3 and 1.7.2 is the way it authenticates to dropbox. In 1.7.2 is authenticates using clear text and 1.7.3 uses encryption, so keep this in mind if this is a concern for you.

What do you mean by “big”? I get it on a backup of about 30mb (15mb compressed).

It took me a long time to find that button too. I think it should be moved.

I’m getting the same error. The log says it finished and the backups are saved where they are supposed to be, but on the job page is says it’s still running.

Downgrading to version 1.7.2 worked for me.

Downgrading to version 1.7.2 made Dropbox work for me.

I just switched over to W3 Total Cache which has a built in CDN with FTP sync and it seems to be working fine.

Thanks anyway.

Thanks for the reply.

I guessed it was a memory issue and tried to increase my limit, but wasn’t able to. I don’t understand why 256mb isn’t enough. I am using a shared host, but this is a pretty common setup so I wouldn’t imagine this would be impossible to do. I’m testing this on a new blog with only one post. I doubt there is even 256mb of data on the whole site including the wordpress install.

I was getting the same ftp error as you, but fixed it by changing the hostname field like you mentioned above.

Now, I’m getting the same memory error you are. It seems the author isn’t interested in people actually using the FTP feature since they’re trying to sell their own service.