• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Allow WPML Multi-stages licenses in wp-config

Hi,
Wordpress-toolkit detect a problem and won't copy data
Could you please provide an error message from WordPress Toolkit?

I've tried to reproduce your case, but the "Copy Data" was finished successfully.
 
[2022-03-03T16:32:07.970-05:00] SiteSyncingInCompletedWithErrors|Data copy from WP installation complete
d (errors)|ERROR|........|18|https://abc.com|Copy Data|Copying of data from https://dev.abc.com to https://abc.com completed with the
following issue: Failed to reset cache for the instance #13: PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 528384 bytes) in /var/www/vhosts/abc.com/dev.abc.com/wp-content/plugins/sitepress-multilingual-cms/classes/utilities/class-debug-backtrace.php on line 137 Fatal error: Allowed memory size of 536870912 bytes exhausted
(tried to allocate 528384 bytes) in /var/www/vhosts/abc.com/dev.abc.com/wp-content/plugins/sitepress-multilingual-cms/classes/utilities/class-debug-backtrace.php on line 137 Err
or: Il y a eu une erreur critique sur ce site.En apprendre plus sur le débogage de WordPress. Il y a eu une erreur critique sur ce site. .

-----------------

if we take out the DEFINE WPML licenses key in both environnements in the wp-config, the error stop.
 
PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 528384 bytes) in /var/www/vhosts/abc.com/dev.abc.com/wp-content/plugins/sitepress-multilingual-cms/classes/utilities/class-debug-backtrace.php on line 137 Fatal error: Allowed memory size of 536870912 bytes exhausted
(tried to allocate 528384 bytes)
That error is not related to WordPress Toolkit.
The error disappears when you remove "define" from wp-config file because in such case the WPML logic is not fully performed, due to lack of valid license key. I can't affirm about this but this is most likely how it works internally.

Looks like the error with "class-debug-backtrace.php" about "Allowed memory size" appears sometimes for WPML users, i've found some topics on WordPress forum and on WPML forum about it, but the solution is not clear.


The simplest way to resolve that error is to set PHP memory_limit to 640M, you can do this in PHP settings (Domains -> your domain -> PHP Settings -> memory_limit), also please check the existence of WP_MEMORY_LIMIT and WP_MAX_MEMORY_LIMIT constants inside wp-config.php, if you see them - increase their value too.


Also I can recommend to report an issue to WPML forum :)
 
Now we have this error :

Failed to reset cache for the instance #13: WordPress Toolkit was not able to finish running an operation on this site in 180 seconds, so the operation was terminated. This could mean that your WordPress installation might be infected with malware. Check the wp-config.php file of the installation for potential malware code or run an anti-virus scan. If you cannot find any traces of malware, try running the operation again later.

But in fact that run more than 15 minutes before to throw the error. This not normal a ~350Mb ishh web site who took normally about 3 minutes to copy become out of memory/time out with 1 more line in the wp-config. The content remain the same in both case. You clearly have a bug or a not implemented support in your tool. The tool clearly doesn't recognise the line and he don't know what to do with it, so considered it as malware stuff.

Thank you!
 
Back
Top