The free forums are no longer in use. It remains available as read-only archive.
i changed to php 5.5 to solve a Wordpress issue on godaddy that made the website unavailable at random times.
After that xcloner is not working anymore:
+The automatic cron job fails telling me to se up the config file, but i cheched and it is already there. I tryed deleting and recreating. Not working
+When i try to do a manual backup the plug is goes on loop (it seems to be loading but it is not) antef i click on continue.
Can anyone help me please?
i'm using the 3.1.2 that is the latest on the wp plugin updater.
I have some news:
+ I managed to get the manual backups working by switching the Normal|Ajax option to normal and waiting a long time. The back up gets done without any information from the page that seems in a loop but it is not. Eventually i get the page that says, the back up is done and i checked with ftp that the backup packet is there.
+ the automatic backup continues Not to work.
Thanks for the support Ovidiu, opening a suport ticket means that i have to pay for the service? And eill you need the wp user name and password?
Thank you for the precise information.
The error of the cron job is this:
Cron <ale****@*****6> /usr/bin/php /home/*******/alessandromaiorana.it/wp-content/plugins/xcloner-backup-and-restore/cloner.cron.php custom_conf1.php
<h2>To run this script you need to create a custom config file inside XCloner Config, and call the script using php cli command like this:</h2>
<strong>php /home/a************/alessandromaiorana.it/wp-content/plugins/xcloner-backup-and-restore/cloner.cron.php mycustomconfig.php</strong>
Ok i've found the way to fix it! 🙂
googling i have realized that it was a matter of how godaddy deal with the php interpreter.
I practice i connected to my server with SSH,
i used “which php5” and “whereis php5”,
i discovered the right path to call php5
and i changed it in the cron job line.
It was not an xcloner issue,
hoever thank you for the support.
May this topic be helful for other people in the same trouble,