The free forums are no longer in use. It remains available as read-only archive.
1:40 pm
May 26, 2011
Hi,
I'm new to XCloner, but it seems to come highly recommended, and I'm hoping you'll be able to help me overcome a small hurdle I'm having with initial testing.
Its installed and creating backups on our source WP site, and I wanted to ensure I could clone this to another host in the event of problems. I can get as far as creating the backup, having XCloner ftp the required bits to the new host and then open the new host XCloner.php page.
The 'installation directory' shows up as:
/home/ohcs219/domains/testim.pale-eds.co.uk/public_html/
but no matter what I do, the error "Directory /home/ohcs219/domains/testim.pale-eds.co.uk/public_html/ is not writeable or does not exists! Could not continue..." comes up. I've tried taking the leading parts off that directory (which as far as I can tell is correct), right down to trying '.' as the install, but still the error. Safe_Mode is configured OFF as shown by phpinfo() link:
PHP Setting | Current Value | Recomemnded |
Open_Basedir: | No value | No Value |
Max Execution Time: | 3600 | >30 |
Safe mode: | Off | Off |
Is there anything else I can try or test to get past this step?
Thanks,
Dave.
3:01 pm
May 26, 2011
Thanks - that worked! Normal permissions were 750, but 777 worked for the clone. However, a few small problems which might be worth reporting:
1) Not critical, but file restore progress went up to 142%!
2) First time round, I left my own phpinfo.php file in the target directory before starting to clone, as I was checking on the safe_mode stuff. But then the restore operation gave an error about being unable to overwrite that file. It wasn't obvious if it that was the only problem, or whether the file restore aborted at that point.
3) The site itself seemed to come across content wise, but the theme options were completely missing. I'm using the Atahualpa theme, which stores its settings in a record in the wp_options table called bfa_ata4. I've looked at the two databases (source and cloned), and these records are very different. Not sure why, or what else might not have 'cloned' - any thoughts on that?
Thanks again for such a quick reply!
Dave.
1) that is normal, since the backup archive is probably a tgz one, so compressed
2) better use an empty directory when restoring, so no other files beside the restore script and backup archive
3) pretty weird, did you use an empty database when restoring? you can check the mysql backup by opening the mysql backup file administrator/backups/database-sql.sql file, inside the backup archive
Ovidiu
3:47 pm
May 26, 2011
Thanks on 1 & 2
Re 3, it was a completely empty database I had just created. I did some more digging, and it seems the Atahualpa theme is very strange regarding its options record. After the clone, I went into the source database and cut&pasted the record via phpMyAdmin into the target, and it still wouldn't stick. When Atahualpa detects any anomoly or error in the options, it simply creates a new, blank options record, erasing everything that you customised.
So it seems that whatever process the cloning used, it didn't like it (perhaps some subtle difference in the configuration of the MySQL databases, etc. I haven't been able to work out).
The theme does have a separate import / export feature which worked, so perhaps it would be possible to work out what's happening from that, but its a shame that it won't be a simple one-click solution via XCloner (as I'll have to remember to back up the them options separately).
I'll ask on the Atahualpa support pages and see if they can help.
1 Guest(s)