Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is experiencing a critical error on their website after installing the WPML String Translation plugin.
Solution:
We recommend enabling the WordPress debug log to identify the specific PHP error causing the issue. To do this, edit the

wp-config.php

file in the WordPress directory and insert the following lines:

define( 'WP_DEBUG', true );<br />define( 'WP_DEBUG_LOG', true );<br />define( 'WP_DEBUG_DISPLAY', false );

After adding these lines, try to reproduce the issue. The debug log will be located in

/wp-content/debug.log

. The client should then paste the content of the debug log on a site like pastebin.com and share the link with us for further assistance.
Relevant Documentation:
https://codex.wordpress.org/Debugging_in_WordPress

If the provided solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your case, we encourage you to open a new support ticket. We also highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please contact us in the WPML support forum.

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.

Tagged: 

This topic contains 1 reply, has 2 voices.

Last updated by Mihai Apetrei 7 months, 1 week ago.

Assisted by: Mihai Apetrei.

Author Posts
April 13, 2024 at 10:44 am #15514707

lionelC-3

Tell us what you are trying to do?
There has been a critical error on this website. Please check your site admin email inbox for instructions. when i instal string translation then my website is broken, i need solution

Is there any documentation that you are following?
Yes

What is the link to your site?

hidden link

Screenshot_3.png
April 13, 2024 at 8:55 pm #15515186

Mihai Apetrei
Supporter

Languages: English (English )

Timezone: Europe/Bucharest (GMT+02:00)

Hi there.

Before this ticket gets assigned to one of my colleagues, I will try to help.

That is a general error message and we can't know what is causing the error until we don't dig a bit deeper.

Let us share the steps that you can use to find out more about what is the actual error when you see a general error message like that one.

We can enable the WordPress debug log and recreate the issue to see if we are getting a longer error message that is more specific.

This will allow us to see if any PHP errors are being produced.

In order to do that, we can edit the wp-config.php file inside our WordPress directory and insert the following lines:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Now, we can try to reproduce the issue once again.

We should now be able to locate the debug log in: /wp-content/debug.log

Paste the content (if any) on a site like pastebin.com and then share the link with us (only you and us will see the URL you are sharing, it is automatically hidden for anyone else).

Relevant Documentation:
https://codex.wordpress.org/Debugging_in_WordPress

Please let us know how things go.

Mihai Apetrei