Forum Replies Created
Feel free to post the warning message here, i have tested this in a clean firefox install and did not receive it here, could it be you have some third party extension that might trigger that?
In your third step, you should be able to select the backup archive to restore the files first(the Restore button near Skip), this unless you have expanded the backup archive manually and you see a ./xcloner-xxxx directory on the server, then you will be able to restore the database.
Let me know if you still have issues.
1. yes, you could restore each subsite manually, however, please note, the restore includes mostly database changes(so it’s only a database restore) since the files are shared between sites.
2. unfortunately not at the moment
3. the restore url is just an API endpoint on any of your subdomains/main domain, it can remain the same for all restores as long as it has access to the filesystem and database
Hope it helps. Ovidiu
You can activate it for each site and it will be able to backup each site separately, or you can activate it globally and it can backup all your network sites, however, the later option is a little bit complicated for restoring a single network site.
It seems the issue might be caused by a browser timeout execution of the script that uploads the backup to the remote storage, are you able to check with your hosting support if you are allowed to increase the execution time?
I suspect this issue would not be appear in the scheduled mode if setup properly through a server cron scheduler.
We had an issue related to this reported issue https://wordpress.org/support/topic/wp-database-backup-tables-excluded/ , it should be fixed in the latest dev version(https://github.com/ovidiul/XCloner-Wordpress/archive/dev.zip), please let me know if you have further issues
This could indicate a timeout on sending the file, do you have any other errors within your XCloner logs from it’s Dashboard?
I’ve posted an update on the latest development package https://github.com/ovidiul/XCloner-Wordpress/archive/dev.zip , please try and reinstall that and see if you have anymore issues.
You should try and reinstall/remove xcloner, it seems the vendor/autoload.php file is missing from it’s plugin folder
You should check your google drive api connection as it might have expired.
During which step you get that error? Usually, that indicates the server is blocking the server request due to high load limit, so you should check with the hosting provider also.
I would suggest to multi-restore setups, specially for localhost ones, to setup a base WordPress installation from where you would launch the restore, and do a restore from it’s panel targeting your development folders and database making sure you can access to them.
So the point is targeting a remote install and not your base one in case of local restores, this if you don’t prefer to download the XCloner restore script and use it’s api endpoint url.
When you are doing a restore to the same installation, files usually get overwritten and while doing that errors might popup, this is not the best way to do a full restore.
The safest way to do a restore is to download the restore script provided in the Restore Panel backend, upload it to the new restore location, can be local or remote, and paste it’s url in the input restore box from the Restore Panel page, that will serve as a standalone API endpoint and can continue the restore process from there.