UpdraftPlus WordPress Backup Plugin - Version 1.2.41

Version Description

01/19/2013 =
Easier Dropbox setup (we are now an official production app)
New button to delete all existing settings
Admin console now displays rolling status updates
Feature: choose how many files and databases to retain separately
Fixed bug with checking access token on Google Drive restore
Fixed bug producing copious warnings in PHP log

Download this release

Release Info

Developer	DavidAnderson
Plugin	UpdraftPlus WordPress Backup Plugin
Version	1.2.41
Comparing to
See all releases

Code changes from version 1.2.40 to 1.2.41

Files changed (3) hide show

methods/email.php +2 -3
readme.txt +1 -1
updraftplus.php +2 -1

methods/email.php CHANGED Viewed

	@@ -13,15 +13,14 @@ class UpdraftPlus_BackupModule_email {
13	wp_mail(get_option('updraft_email'), "WordPress Backup ".date('Y-m-d H:i',$updraftplus->backup_time), "Backup is of the $type. Be wary; email backups may fail because of file size limitations on mail servers.", null, array($fullpath));
14	$updraftplus->uploaded_file($file);
15	}
16	-
17	- $updraftplus->prune_retained_backups("local", null, null);
18	}
19
20	function config_print() {
21	?>
22	<tr class="updraftplusmethod email">
23	<th>Note:</th>
24	- <td>If choosing "E-Mail", then be aware that mail servers tend to have size limits; typically around 10-20Mb; backups larger than any limits will not arrive. If you really need a large backup via email, then you could fund a new feature (to break the backup set into configurable-size pieces) - but the demand has not yet existed for such a feature.</td>
25	</tr>
26	<?php
27	}


13	wp_mail(get_option('updraft_email'), "WordPress Backup ".date('Y-m-d H:i',$updraftplus->backup_time), "Backup is of the $type. Be wary; email backups may fail because of file size limitations on mail servers.", null, array($fullpath));
14	$updraftplus->uploaded_file($file);
15	}
16	+ $updraftplus->prune_retained_backups("email", null, null);

17	}
18
19	function config_print() {
20	?>
21	<tr class="updraftplusmethod email">
22	<th>Note:</th>
23	+ <td>The email address entered above will be used. If choosing "E-Mail", then be aware that mail servers tend to have size limits; typically around 10-20Mb; backups larger than any limits will not arrive. If you really need a large backup via email, then you could fund a new feature (to break the backup set into configurable-size pieces) - but the demand has not yet existed for such a feature.</td>
24	</tr>
25	<?php
26	}

readme.txt CHANGED Viewed

	@@ -34,7 +34,7 @@ UpdraftPlus is written by professional WordPress developers. If your site needs
34
35	= Other support =
36
37	- We hang out in the support forum for this plugin - http://wordpress.org/support/plugin/updraftplus - however, to save our time so that we can spend it on development ~~and not repeating ourselves~~, please read the plugin's Frequently Asked Questions ((http://wordpress.org/extend/plugins/updraftplus/faq/) before ~~you~~ ~~submit any support requests~~, and ensure that you have updated to the latest released version of UpdraftPlus.
38
39	== Installation ==
40


34
35	= Other support =
36
37	+ We hang out in the support forum for this plugin - http://wordpress.org/support/plugin/updraftplus - however, to save our time so that we can spend it on development, please read the plugin's Frequently Asked Questions - http://wordpress.org/extend/plugins/updraftplus/faq/ - before going there, and ensure that you have updated to the latest released version of UpdraftPlus.
38
39	== Installation ==
40

updraftplus.php CHANGED Viewed

	@@ -17,8 +17,9 @@ TODO
17	//?? On 'backup now', open up a Lightbox, count down 5 seconds, then start examining the log file (if it can be found)
18	//Should make clear in dashboard what is a non-fatal error (i.e. can be retried) - leads to unnecessary bug reports
19	//Eventually, when everything can be resumed, we will no longer need the backup() routine; it can be replaced with the resume() routine
20	- // Should we resume if the only errors were upon deletion (i.e. the backup itself was fine?) Presently we do, but it displays errors for the user to confuse them. ~~Perhaps better to make pruning a separate scheuled task??~~
21	// Make jobs individually resumable (i.e. all the state info must be keyed on the nonce; then call the resume event specifying the nonce)

22	// Warn the user if their zip-file creation is slooowww...
23	// Create a "Want Support?" button/console, that leads them through what is needed, and performs some basic tests...
24	// Resuming partial FTP uploads


17	//?? On 'backup now', open up a Lightbox, count down 5 seconds, then start examining the log file (if it can be found)
18	//Should make clear in dashboard what is a non-fatal error (i.e. can be retried) - leads to unnecessary bug reports
19	//Eventually, when everything can be resumed, we will no longer need the backup() routine; it can be replaced with the resume() routine
20	+ // Should we resume if the only errors were upon deletion (i.e. the backup itself was fine?) Presently we do, but it displays errors for the user to confuse them.
21	// Make jobs individually resumable (i.e. all the state info must be keyed on the nonce; then call the resume event specifying the nonce)
22	+ // Separate 'retain' settings for db + files (since they are on separate schedules)
23	// Warn the user if their zip-file creation is slooowww...
24	// Create a "Want Support?" button/console, that leads them through what is needed, and performs some basic tests...
25	// Resuming partial FTP uploads