Caspar
Forum Replies Created
-
Hi Tbone17,
thanks for your feedback, we appreciate it! 🙂
Your log file doesn’t show any warning whatsoever, so we’ll have to dig a bit deeper here.
First of all, I’d ask you to double-check if all files and folders included in the backup job are readable for BackWPup. Permissions of 0755 for folders and 0644 for files would be sufficient. BackWPup usually warns in the log file when it cannot read fiels or folders, but just in case let’s make sure permissions are set correctly.Once you verified permissions, please re-configure your backup job and set Archive Format to Tar GZip just for the sake of testing. Does that produce the same result?
Forum: Plugins
In reply to: [BackWPup – WordPress Backup & Restore Plugin] Russian translationHi VBog,
thanks a bunch for providing russian translation for BackWPup! We’ll definitely add it to the next release and get in touch with you about the whats, hows and wheres for future releases.
Cheers,
CasparForum: Plugins
In reply to: [BackWPup – WordPress Backup & Restore Plugin] How to disable archive mode?Btw, BackWPup Pro does provide a synchronisation feature which does not compress backup files. 😉
Forum: Plugins
In reply to: [BackWPup – WordPress Backup & Restore Plugin] How to disable archive mode?Hi 3×7,
thanks for your feature request, I’m going to pass it on.
Stay all backed up! 🙂
CasparForum: Plugins
In reply to: [BackWPup – WordPress Backup & Restore Plugin] Optimise and checkYes, it might. 🙂 One job to check, another one to optimize.
Forum: Plugins
In reply to: [BackWPup – WordPress Backup & Restore Plugin] 3.0.10 Fatal ErrorCheck if sdk/Aws/Symfony/Component/ClassLoader/UniversalClassLoader.php exists in the backwpup plugin folder. If it does as it should, verify that the path is readable.
If that’s the case and the error is still there, I’d consider reinstalling the plugin.[Setting the topic to Not a support question since that’s what it is not.]
Hey Joerg,
you can try this solutions:
http://ww.wp.xz.cn/support/topic/309-still-has-probs-uploading-to-dropbox?replies=3#post-4150263Cheers,
CasparAs I said before, you can re-upload and re-implement those images with shorter file namens.
You can also contact your web host about this line:
[INFO] Maximum script execution time is 30 seconds
and ask them if/how you can set a higher value for maximum script execution time, like 60 or 90 seconds.@mbrsolution To be precise, it’s not an error, it’s a warning:
[05-May-2013 16:59:33] WARNING: File "/home/[..]/stats/logs" is not readable!So it says right there: not readable. That’s all the warning is about, and as it is a only a warning, not an error it doesn’t stop the running process (your backup) from being completed.
The second warning looks a bit different, it says:
[05-May-2013 16:59:33] WARNING: Link "/home/[..]/stats/error_logs" not followed.So
error_logsseems to be a link (most likely an alias for another directory in this case) which BackWPup does not follow. That’s correct behavior, because otherwise everything in that directory would be included in the process.BackWPup, or PHP actually, is simply saying: “Hey, you wanted me to do this and that, but I can only do this, not that, and I thought I’d better let you know.”
Try going setting your job back to tar.gz then, go to the Fiels tab and exclude the 2012 folder.
Forum: Plugins
In reply to: [BackWPup – WordPress Backup & Restore Plugin] 3.0.10 Fatal ErrorWhich PHP version does your site run upon?
Nope, that’s a different warning. Now you have a bunch of images with filenames too long to be saved in a TAR archive. Try ZIP instead, or better yet, re-upload those images with shorter filenames.
Forum: Plugins
In reply to: [BackWPup – WordPress Backup & Restore Plugin] Error Sending Back Up to EmailFinally, it looks like this is not a plugin support issue, but an issue with PHP lower than 5.3. See this thread in Trac.
is_a()has been un-deprecated in PHP 5.3.Forum: Plugins
In reply to: [BackWPup – WordPress Backup & Restore Plugin] Cannot authorize DropboxFor the record, there are a couple of possible causes to this issue:
- WordPress cannot make external requests (host resticitons)
- A caching plugin caches transients, so BackWPup is served a wrong authcode or no authcode at all.
- Another plugin may be interfering.