JoomlaPlug!

hey there everyone

well The time has come for us to backup and clone our live sites to a local development core server, so we whipped out the ol joomla cloner, we did upgrade to v1.92 i beleive,

I am not sure if this was all a result of the defects in the component or our hosting, so i am posting here,

you can watch the FULL VIDEO we did and see the steps we take and of course the sad results

(on a postive note it DOES clone the site, however the cloned site is hosed, we use something called multithumb and joomlacomment on the live site, and as you can see it works fine, so something went REAL WRONG in the backup and clone process.

See for yourself,

the site we tested our clone on is at
http://www.zteknologies.com/ourworld

and the video including the cloned site after moving and restore can be found at
http://www.zteknologies.com/filestore/joomlaclonerjunk/Untitled.html


as i siad if someone (admin or other) spots something we are doing wrong PLEASE let me know, so we can try to get ALL THE sites working, this component WHEN IT WORKS continues to amaze me, right now we are taking another HARD look at joomlapack as well, but there are issues on that front as well

thanks again

The issues you have there are as follow:

1. make sure on restore the "Install dir:" and "Install url:" point to the correct location, i noticed an incorrect restore url there

2. the database issue you have is caused by a compatibility problem within the mysql backup site and the restore, to fix it i suggest you recreate the backup and look on the Generate backup screen, database options tab for the "Mysql compatibility" field, try to set that to MYSQL40 if your new mysql restore server is that version or newer

One more thing, when doing the restore again, make sure you delete the administrator/backups folder from the restore site, and also try and check the "incremental sql import" from the Joomla.Cloner.php screen

Regards, Ovidiu

As for the warnings you get there on frontpage, that is a issue from your server configuration, i would advise adjusting the php.ini file to include that deprecated settings

ovidiu

ok so far i redid the backup

heres where we are at

1. the backup seems to have been successful
2. during backup i used the MYSQL compatibility 4.0 which solved A LOT OF ERRORS

3. on restore i entered in the correct URL, and did incremental restore

4. the site restored but still the multithumb component and joomlacomment component are still hosed in the restored site,

You mentioned depreciated values in php, why is it doing this in the first place, the live site shows no signs of this, and if joomlacloner "is supposed to CLONE the site perfectly" shouldnt these errors not exist, even so, whats the easiest suggestion to get the multithumb component working with the restored site, (in other words get rid of those errors)

5 and finally this screenshot was the only error during restore, there were 3 or so of these, though i'm not sure what they mean

were getting closer, but joomlacloner still has yet to DUPLICATE an entire site to my satisfaction, but thanks so much for the continued help

remaining error
http://www.zteknologies.com/filestore/joomlaclonerjunk/joomlaclonernewerror062208.jpg

The error you get there can be skipped, those are some extra queries which you won't need to import on this host!

As for the deprecated values issues, JoomlaCloner is unable to fix that since it depends on each server php configuration and how a component is coded!

I would advise to reinstall the extensions you have issues with, and if the error persists to contact the appropriate developers for further support

Regards, Ovidiu

ok it seems after one more final backup that all works well, this is still avery buggy solution (we will test it on the next few sites) but it does the job ok, the multithumb thing turned out to be a case of absolute paths in the iamges , which broke that link

the other issues could not be resolved, we tried to search through the class.php but no info was given to what to change, and as far as we know there is no "INI" that we could spot

thanks for all the help!