The free forums are no longer in use. It remains available as read-only archive.
Log In
Topic RSS
9:27 pm
March 2, 2011
Offline
I think the problem is possibly a server issue as I have made a fresh install of wordpress and atahulaha into a clean database and this is still scambling the page. WordPress on its own was ok but once the atahulaha is installed things go wrong. I have tried a number of installs and all seem to have the same problem.
The other thing that I notice is that on my server i can create a database in any name that I like but in the new server databases are prefixed with a name for example home/name so a data called jumbo on my server would just be jumbo but on the new server it would ne name_jumbo.
Raz
9:59 pm
September 26, 2010
Offline
atahulaha is this plugin http://wordpress.org..... right?
Thanks for sharing this!
Regarding the database prefix, that is usually the case also on most cpanel control panels, mysql user and database name get prefixed with the cpanel username.
Ovidiu
10:14 pm
March 2, 2011
Offline
I have found the problem and it seems there is a conflict with the latest version of atahualpha and Suhosin so I guess that counts out a clone transfer. I have instlled a lower version of atahualpha and that works fine so it looks like a rebuild. Thankfully, atahualpha lets you export your settings so half the job is done.
9:42 am
March 2, 2011
Offline
My problem is now resolved and the solution was to upload a php.ini file into the root directory as per this thread http://forum.bytesfo.....hp?t=12262
So in essence if people have sites built with the wordpress theme atahualpa and their server has Suhosin then the clone will not fully install until the php.ini file in uploaded.
5:11 pm
September 26, 2010
Offline
Awesome, glad you got it working! Ovidiu
4:26 pm
October 27, 2011
Offline
I had the original error posted at the start of this thread – this thread helped me eventually fix my problem – just in case there are any other nutters out there who, like me, dabble in stuff they don't understand, this is what I did to fix my own XCloner restore:
I have downloaded my XCloner backups from my original web-based site and then installed them (i.e. "restore") to a virtual machine (running Turnkey WordPress) running on my laptop (running Ubuntu 10.04).
By trial and error I muddled through (I am a newbie) (the original instructions did not seem to work)(also it does not matter when I trash wordpress because it only takes a few minutes to re-install another VM wth WP)(I trashed it five times during the last three days discovering the stuff below) This is what I did instead that seems to work *beware* it might be the wrong way to do it!:-
1. In the wordpress directory e.g. in the virtualisation it is:-
/var/www/wordpress
create administrator and backups to produce this:-
/var/www/wordpress/administrator/backups
and then make backups writeable:
chmod a+w /var/www/wordpress/administrator/backups
2. Put the backupxxxxxx.tar file(s) in the wordpress directory (not in administrator/backups) i.e. in
/var/www/wordpress/backup.xxxxx.tar
/var/www/wordpress/backup.xxxxx.1.tar
/var/www/wordpress/backup.xxxxx.2.tar
3. Log in to wordpress via your browser and install the XCloner plugin.
4. Copy XCloner.php and TAR.php (if missing then install XCloner plugin) from here:
/var/www/wordpress/wp-content/plugins/xcloner-backup-and-restore/restore
to the same place i.e. to
/var/www/wordpress/XCloner.php
/var/www/wordpress/Tar.php
5. In browser, discover the mysql password by logging into wordpress as admin (with PW you created earlier) and then in XCloner go to administration (I think) and click the mysql tab and copy the password (the user name will be there too i.e. "wordpress")
6. Run the XCloner restore php file in your browser like this:-
192.168.122.111/XCloner.php
(that 192.168.122.111 business is evidently my local ip of my virtual machine's wordpress – your URL will be different)
and paste the password in (and type "wordpress" into the two other boxes) and press the button.
I got an "…unable to write error…" and had to do a
chmod a+w *
to the
/var/www/wordpress
And then all files installed, more or less, I got one error with a .png that failed to "…write to binary…" (same as original starting-post to this thread) or similar, and another about "…failed to install database-sql.sql…" then I hit the install to database link and lots and lots and lots of duplicate-errors in mysql data so…
…clear out the database by…
7. Wiping mySql database clean via phpmyadmin via port 12322 e.g.
192.168.122.111:12322
When you first log in (username == root, pw == the one you supplied earlier) you need to crash through the warnings and take the certificate created for you and then, once in, click the database tab (left most) and clicking the database (wordpress) and then ticking all tables and then dropping them all.
So repeat 6. by backspacing firefox to the XCloner window where you pasted your huge-long-mysql-password and hit that submit again, this time, the database is allowed to be populated without errors and it eventually all fires up OK.
I could not log into wordpress via
192.168.122.111/wp-admin
(because I wiped the database?) so enter phpmyadmin again via e.g.
192.168.122.111:12322
and again click on the database (wordpress) and then click the sql tab and paste this in:
UPDATE `wp_users` SET `user_pass` = MD5( "your_password_here" ) WHERE `wp_users`.`user_login` = "user_name_here"
change the password and user name to what to want and hit "go".
8. Delete XCloner.php and TAR.php and the backup files in
/var/www/wordpress
9. I can no longer log into XCloner ( I guess that was what the the failure to install database-sql.sql meant during 6. above? ) so I deactivate it and delete it and then re-install XCloner.
All my blog is there! (I don't care about the missing backups)(I can take a snapshot of the entire VM, it takes 5 minutes and is about 300Mbytes).
Another thing I discovered, one of my original backupxxxxx.1.tar files was 2.2 Gbytes, this was because it contained all my original backup files, in my first experiments, it was taking about fifteen to twenty minutes during the XCloner.php restore, so I unpacked it, removed all the backups and packed it up again and reduced the size to ~300Mbytes, and then it loaded much quicker.
1 Guest(s)
