Touda

Good news! Fortunately the free version of the plugin you suggested just did the trick! It’s compatible with Polylang: https://docs.domainmappingsystem.com/integrations-and-compatibility/wordpress-plugins/polylang

So, thank you for the reference, Matthias!

Sadly we cannot afford to pay those prices, even if it would work with Polylang ??

I think we’ll have to drop your plugin and search for an alternative.

Thanks for your help.

Thank you very much, Rolf, for the quick and complete explanation. Yes, I guess it wouldn’t be too dificult to make that variant plugin – it’s a great idea indeed, and I will send you that message right now ??

Sad to read that, Matt ??

Will that premium version work with Polylang?

I’ve tried to manually add edit_comment permission to User Role Editor panel and to explicitly disable it there, but it has not worked: emails are still sent to Contibutors (posts’ authors) and not to site’s Admin.

More info:
Not ALL inner URL keep the alternative domain name: those related to the home page, in both languages, do jump:
https://anpamilla.gal/gl
https://anpamilla.gal/es
https://anpamilla.gal/inicio
https://anpamilla.gal/inicio-gl

May it gives you some clue of what’s happening?

Tried to uncheck automatic language recognition at Polylang settings and it didn’t fix the issue.

Anyway there is still an automatic jump because Polylang knows that /gl/ is the main language so when you go to the home page (no matter with which domain name), it makes the browser jump to /gl/ subdirectory. Maybe it’s forcing it as ANPADOIESDOMILLADOIRO.COM/gl instead of a relative /gl/ jump? (When you use Polylang there has to be always, at least, this first jump.)

Do you know if there is some incompatibility between your plugin and Polylang at this level?

With the help of our hosting company we found the problem in the end. It was related to another plugin, WordPress Download Manager. It happened that a folder created by this plugin had an enormous number of files (even though we don’t have more than 40 downloadable files). It was located at /wp-content/uploads/wpdm-cache/ and made XCloner to stop (Error 500) even when we tried to list the folders contents at the File exclusion tab.

It was hard to find because neither the server nor WordPress nor XCloner itself registered any information about this problem at the various logs.

As soon as we excluded the whole cache directory of WPDM plugin, XCloner did the whole backup without a problem.

I know it’s not XCloner fault, but maybe this could give some indications to the creator team for future improvements – to be able to detect such circunstances found at the file tree and give information to the user so (s)he can fix it.

Here you have the last lines of the XCloner inner debug file. As you can see, no hint is given on the reason for this failure ??

[2021-08-01 07:31:54] xcloner_file_system.INFO: Adding wp-content/uploads/2021/07/vivir-maria-gonzalez-reyes-portada-virginia-pedrero-w360.jpg to the filesystem list ["FILESYSTEM SCAN","INCLUDE"] []
[2021-08-01 07:31:54] xcloner_file_system.DEBUG: Storing wp-content/uploads/2021/07/vivir-maria-gonzalez-reyes-portada-virginia-pedrero-w360.jpg in the backup list [] []
[2021-08-01 07:31:54] xcloner_file_system.DEBUG: Building the files system list [] []
[2021-08-01 07:31:54] xcloner_file_system.DEBUG: Building the files system list [] []
[2021-08-01 07:31:54] xcloner_file_system.DEBUG: Checking if wp-content/uploads/wpcf7_uploads/.htaccess is excluded [] []
[2021-08-01 07:31:54] xcloner_file_system.INFO: Adding wp-content/uploads/wpcf7_uploads/.htaccess to the filesystem list ["FILESYSTEM SCAN","INCLUDE"] []
[2021-08-01 07:31:54] xcloner_file_system.DEBUG: Storing wp-content/uploads/wpcf7_uploads/.htaccess in the backup list [] []
[2021-08-01 07:31:54] xcloner_file_system.DEBUG: Building the files system list [] []
[2021-08-01 07:32:14] xcloner_file_system.INFO: Cleaning the backup storage LOCAL on matching rules [] []
[2021-08-01 07:32:14] xcloner_file_system.DEBUG: Estimating file system reading time [] []
[2021-08-01 07:32:14] xcloner_file_system.DEBUG: Deleting the temporary storage folder /home/quince/public_html/webzine/wp-content/backups-R1Fs3//.xcloner-ea11f [] []
[2021-08-01 07:32:19] xcloner_file_system.DEBUG: Deleting the temporary storage folder /home/quince/public_html/webzine/wp-content/backups-R1Fs3//.xcloner-ea11f [] []
[2021-08-01 07:35:56] xcloner_file_system.INFO: Cleaning the backup storage LOCAL on matching rules [] []
[2021-08-01 07:35:56] xcloner_file_system.DEBUG: Estimating file system reading time [] []
[2021-08-01 07:35:56] xcloner_file_system.DEBUG: Deleting the temporary storage folder /home/quince/public_html/webzine/wp-content/backups-R1Fs3//.xcloner-ea11f [] []

By the way, when backing up this site, XCloner sucks 50% or more of the CPU of our server, as I have monitored.

Now the last errors are happening when XCloner scans the same file. Once again it’s a JPG file, though it’s a different one from the one we referred in our first message.

Memory limit increased from 256 to 512 MB and still getting the same errors. Yet no trace of those errors is being logged at server level nor with WP debug mode on ?? So we are completly at a lost with this!

Yes, XCloner knows to deal with big size installations.

And can it handle low memory availability? We got a 128 MB limit and these problems keep on happening on and on, and we are not able to backup this site since many months now ??

All the other sites, with less size, that we host at our server are being backup’ed without a problem.

Oh, really? I feel ashamed for the confussion! I usually only click on the links through the plugins panel to make sure that I arrive to the right plugin, but I don’t seem to have done so this time :-/

Anyway, now that I’ve arrived here… could your plugin be a good replacement for that abandoned one? Has it similar funcionalities?

Strangely, when I went to plugins panel instead of updates panel, and click on “update” for WooCommerce plugin, no warning about compatibility of your plugin appeared and WC’s update was done without a problem.

Anyway, WordFence secutrity plugin keeps on showing me a warning about your plugin being abandoned. (?!?)

I’ve posted a capture of that warning but couldn’t get it to show in English, sorry.

As far as I know there is no modification of your plugin. If it was, Wordfence should warn about it, shouldn’t it?