Themes are not updating because backup is failing without errors.
Hi there, I've got the-retailer 1.8.6 installed. You're plugin detected a new version, but automatic update doesn't work. It starts, but stucks and hows an empty screen. There aren't any errors in the php-errorlog. What could be wrong?
kind regards, Dennis
What is "the-retailer 1.8.6"?
Is that a theme?
Yeps. http://themeforest.net/item/the-retailer-responsive-wordpress-theme/4287447
Which version of the plugin are you using?
1.7.1 sorry I hadn't mentioned that before ;-)
I'm not having any issues getting updates or installing themes on my system. Do you have other themes you've purchased but not installed yet? If so, could you try installing one. By clicking the install automatically link the theme will install but not activate so if this is a live site it will not effect anything. Let me know if you are able to install. If you don't have any other themes it's a bit harder to troubleshoot through process of elimination.
I'm affraid I don't have any unused purchased themes. It's not clear to me if the process stalls in downloading, executing or anywhere else. Any ideas how to debug the process?
Back up you theme before going any further. You can do that via FTP by navigating to the wp-content/themes/ directory and making a copy of your theme there.
Then, install the Query Monitor plugin and look at the HTTP requests for errors when you attempt to update. When you try to update look up at the top of the page for a dropdown next to +New navigation item. This will have a ton of useful information, if there is something going wrong.
https://wordpress.org/plugins/query-monitor/
Is this helpful?

Turn off the github updater in the settings.
check ... 'did just that. Errors from the screendump don't occur no more, update still isn't working though
Hi there, Finally got it to work. I unchecked the Theme backup option!
So then there is something about your server that doesn't allow it to make backups and fails without explanation. I'll leave this issue open and look into it some more for the next version.
Please test the hotfix-1.7.2 branch to see if this is still an issue. However, with out more to go on it's unlikely I'll be able to fix this.