craigmbooth
Forum Replies Created
-
Forum: Plugins
In reply to: [UpdraftPlus: WP Backup & Migration Plugin] Backup of plugins failsI have no idea why this fixed it, it could just be the total size of the plugins directory. When I removed the plugin ‘widgetize-pages-light’ the process went just fine.
Forum: Plugins
In reply to: [UpdraftPlus: WP Backup & Migration Plugin] Backup of plugins failsI should also add that after sitting like that for a while, it starts upa second backup process that seems to notice an untouched .zip.tmp file and tries again, but also hangs with the tail of the logfile looking like this:
0001.636 (0) backup_2013-09-17-1655_A_Dear_School_Podcast_62f7b2860978-plugins.zip.tmp: size is now: 5.20 Mb 0301.828 (1) Opened log file at time: Tue, 17 Sep 2013 17:00:20 +0000 0301.829 (1) UpdraftPlus: 1.7.18 WP: 3.6.1 PHP: 5.3.27 (Linux assmule.apisnetworks.com 3.10.1 #5 SMP Tue Jul 30 22:46:46 EDT 2013 i686) MySQL: 5.0.90-community Server: Apache safe_mode: 0 max_execution_time: 900 memory_limit: 256M (used: 2.8M | 3M) ZipArchive::addFile: Y 0301.830 (1) Free space on disk containing Updraft's temporary directory: 15291.6 Mb 0301.831 (1) Backup run: resumption=1, nonce=62f7b2860978, begun at=1379436918 (302s ago), job type=backup, previous check-in=1.6s 0301.832 (1) Scheduling a resumption (2) after 300 seconds (1379437520) in case this run gets aborted 0301.842 (1) Checking if we have a zip executable available 0301.843 (1) Testing: /usr/bin/zip 0301.854 (1) Output: adding: binziptest/subdir1/ (in=0) (out=0) (stored 0%) 0301.855 (1) Output: adding: binziptest/subdir1/subdir2/ (in=0) (out=0) (stored 0%) 0301.856 (1) Output: adding: binziptest/subdir1/subdir2/test.html (in=127) (out=105) (deflated 17%) 0301.856 (1) Output: total bytes=127, compressed=105 -> 17% savings 0301.867 (1) Output: adding: binziptest/subdir1/subdir2/test2.html (in=134) (out=109) (deflated 19%) 0301.868 (1) Output: total bytes=261, compressed=214 -> 18% savings 0301.869 (1) Error output: 0301.869 (1) Error output: 0301.869 (1) Error output: 0301.885 (1) Working binary zip found: /usr/bin/zip 0301.886 (1) Zip engine: found/will use a binary zip: /usr/bin/zip 0301.886 (1) Creation of backups of directories: had begun; will resume 0301.889 (1) Beginning creation of dump of plugins (split every: 800 Mb) 0301.890 (1) File exists (/home/virtual/site154/fst/var/www/adearschool/wp-content/updraft/backup_2013-09-17-1655_A_Dear_School_Podcast_62f7b2860978-plugins.zip.tmp), but was apparently not modified within the last 30 seconds, so we assume that any previous run has now terminated (time_mod=1379436920, time_now=1379437220, diff=300) 0301.941 (1) backup_2013-09-17-1655_A_Dear_School_Podcast_62f7b2860978-plugins.zip.tmp: Zip file already exists, with 501 files 0302.223 (1) Remaining entities to add to zip file: 85 directories, 512 files 0302.240 (1) Zip: backup_2013-09-17-1655_A_Dear_School_Podcast_62f7b2860978-plugins.zip.tmp: 100 files added (on-disk size: 5297.1 Kb) 0302.255 (1) Zip: backup_2013-09-17-1655_A_Dear_School_Podcast_62f7b2860978-plugins.zip.tmp: 200 files added (on-disk size: 5297.1 Kb) 0302.272 (1) Zip: backup_2013-09-17-1655_A_Dear_School_Podcast_62f7b2860978-plugins.zip.tmp: 300 files added (on-disk size: 5297.1 Kb) 0302.287 (1) Zip: backup_2013-09-17-1655_A_Dear_School_Podcast_62f7b2860978-plugins.zip.tmp: 400 files added (on-disk size: 5297.1 Kb) 0302.301 (1) Zip: backup_2013-09-17-1655_A_Dear_School_Podcast_62f7b2860978-plugins.zip.tmp: 500 files added (on-disk size: 5297.1 Kb)The net results is that I have two backup processes stuck on the stage “Creating file backup zips (Plugins)”
Forum: Plugins
In reply to: [Plugins List] Warning upon activating pluginIt appeared at the top of every single page in the admin panel. Making the change I mentioned in the first post (adding quotation marks around the first argument of define() on L22 of plugins-list.php) made the warning disappear immediately.
I’m not a PHP expert, but maybe the PHP install on my server was set up to be very aggressive with reporting warnings, it didn’t affect the operation of the plugin itself (as the notice says, PHP assumed we meant for the quotes to be there and corrected it), it was just an annoying message.