When i installed WPML String Translation then why is showing critical error?

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

This topic contains 4 replies, has 3 voices.

Last updated by Bobby 10 months ago.

Assisted by: Bobby.

Author	Posts
February 13, 2024 at 2:35 am #15295324
lionelC-3	Tell us what you are trying to do? When i installed WPML String Translation then why is showing a critical error? Is there any documentation that you are following? Yes What is the link to your site? hidden link
February 13, 2024 at 5:10 am #15295441
Mihai Apetrei Supporter Languages: English (English ) Timezone: Europe/Bucharest (GMT+02:00)	Hi there. Before this ticket gets assigned to my colleagues, I will try to help. 1. Usually, the 500 errors (Internal Server Errors) are related to the server configuration or server limitations being reached. You can check our documentation to see if you meet all the WPML minimum requirements here: https://wpml.org/home/minimum-requirements/ 2. Also, please take a look here: https://wpml.org/faq/500-error 3. You can also activate WordPress debug to find out more about what is actually happening when you receive that 500 error: https://wpml.org/documentation/support/debugging-wpml/ 4. This issue might also be caused by incompatibility or not 100% compatibility between WPML and (at least) one of the active plugins or the active theme. Can you please try to see if this issue happens even when only the WPML plugins are active and you are using a default WordPress theme? Please try the following steps so that we would test for a compatibility-related issue: - create a full website backup  - disable all plugins except WPML and its add-ons  - check if the issue is happening again  - if it's not, reactivate your plugins one by one, checking every time if the issue shows up again so that you can understand which plugin is causing that issue If the issue happens even with the non-WPML plugins disabled: - leave all the non-WPML plugins deactivated  - switch to a default theme like TwentySeventeen  - try to recreate the issue now If you have the chance, it would be best to do this in a staging (testing) environment. I hope that you will find this information helpful. Please let us know how things go. Mihai Apetrei
February 13, 2024 at 9:10 pm #15299586
lionelC-3	I haven't found a solution for this yet please kindly see this attached photo.
February 13, 2024 at 9:15 pm #15299648
lionelC-3	Please check this
February 14, 2024 at 1:30 am #15300004
Bobby Supporter Languages: English (English ) Timezone: America/Los_Angeles (GMT-08:00)	Hello, Thank you for sharing the above information, to get a better idea of the error I would need to see the details of the error. You can see how to enable debug logging here: https://wpml.org/documentation/support/debugging-wpml/ Go in your wp-config.php file and look for define(‘WP_DEBUG’, false);. Change it to: define('WP_DEBUG', true); Edit your wp-config.php file and add these lines, just before it says 'stop editing here': ini_set('log_errors',TRUE); ini_set('error_reporting', E_ALL); ini_set('error_log', dirname(__FILE__) . 'https://cdn.wpml.org/error_log.txt'); This will create an error_log.txt file in your site's root directory. Please send me its contents.