The free forums are no longer in use. It remains available as read-only archive.
3:38 pm
September 30, 2010
I just installed the Xcloner plugin and after finishing configuring I am looking in the info section and I have this warning
Temporary Folder | /usr/share/wordpress//administrator/backups incorrect or unreadable this path needs to be created and be writeable in order for XCloner to work properly |
This makes sense, since I don't have a folder /usr/share/wordpress//administrator/backups, and I cannot create one in my box either because of the double slash. I changed the backup directory, but I have not find anywhere where to change the temporary folder
4:40 pm
September 26, 2010
Hi there! What is the value of the Backup Start Path option in your XCloner Config?
As per our install instructions, there is a special folder that always need needs to exist inside the Backups Start Path you configured in XCloner, and that is administrator/backups , you need to also make it fully writeable.
Please check also the wiki instructions https://docs.xcloner.com/#/
Hope it helps! Ovidiu
10:05 pm
September 30, 2010
Well, look at that 🙂
I had already created the folder administrator/backups. However it fixed the error after I removed the trailing slash from the Backup Start Path.
After saving info was showing green, but still shows /usr/share/wordpress//administrator/backups as the temporary folder. Most likely because after saving the trailing slash is back into the backup start path.
However I run a backup manually and it completed.
Just one quick note, I searched the PDF manual, and there was no mentioning of the temporary folder on it. I will refer to the wiki next time just in case 🙂
2:28 pm
October 21, 2010
I'm experiencing a very similar problem and it seems to render Xcloner useless.
I have created the administrator/backups directory at the root of my wordpress site and it is fully readable and writable, but when i try to create backup I get a slew of errors:
Warning: fopen(/ ... /wp-blog-netfirms//administrator/backups/database-sql.sql) [function.fopen]: failed to open stream: Permission denied in / ... /wp-blog-netfirms/wp-content/plugins/xcloner-backup-and-restore/cloner.functions.php on line 1863
Warning: fopen(/ ... /wp-blog-netfirms//administrator/backups/perm.txt) [function.fopen]: failed to open stream: Permission denied in / ... /wp-blog-netfirms/wp-content/plugins/xcloner-backup-and-restore/cloner.functions.php on line 1257
TAR error: File '/ ... /wp-blog-netfirms//administrator/backups/index.html' does not exist
Starting the manual backup process!
Database backup: d60695889: Backup FAILED, please check that administrator/backups directory is writeable!Backup / ... /WP-backups/xcloner-backups/backup_2010-10-21_10-24_ovaloffice.ca-sql-nodrop.tar created, we may continue!
Please click here to continue!Warning: fopen(/ ... /wp-blog-netfirms//administrator/backups/perm.txt) [function.fopen]: failed to open stream: Permission denied in / ... /wp-blog-netfirms/wp-content/plugins/xcloner-backup-and-restore/cloner.functions.php on line 890
Total process: % out of 0 files
Processing files 0 to 0 for backup file /mnt/w0501/d45/s17/b02c59fa/www/ovaloffice.ca/WP-backups/xcloner-backupfolder/backup_2010-10-21_09-55_ovaloffice.ca-sql-nodrop.tar!
Current backup size: 1 KBUnable to continue, could not open file / ... /wp-blog-netfirms//administrator/backups/perm.txt for reading!
Any ideas what might be going wrong?
6:12 pm
October 21, 2010
It seems like you're right, there was something really odd going on with the permissions. I had been using the Fetch ftp client and it was telling the permissions for that folder were 777. After your reply i got suspicious and I tried the Cyberduck client instead. Indeed Cyberduck indicated different permissions on the folder! After repeatedly resetting the folder permissions both ftp clients now agree that they are 777 and also the backup seems to work now.
I just have a couple questions:
Is 777 the correct permissions setting for this folder?
Excuse me for being a nube but why do you put a double-slash in the path "wp-blog-netfirms//administrator/backups"? What does that mean?
Thanks!!
777 is correct, but you might want to try also 666 on that directory for security reasons
As for double slash, you can remove that and replace it with a single slash, it might have something to do with the default folder assignment, will look into that, however it should not affect the backup process.
Ovidiu
12:59 pm
December 2, 2010
Hi,
I get something similar. My info page reports:
C:/wamp/www/drupal-6.19//administrator/backup incorrect or unreadable
..which would make sense, given the double slash.
Mybackup start path is 'C:/wamp/www/drupal-6.19/' but when I try & remove the trailing slash, it is re-inserted aurtomatically when I save.
Kind of odd!
Thanks
Bill
1 Guest(s)