Skip to content Skip to sidebar

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 1 reply, has 0 voices.

Last updated by lawrenceA-3 9 months ago.

Assisted by: Andrey.

Author Posts
March 12, 2025 at 9:17 am #16805836

lawrenceA-3

Background of the issue:
I am trying to find the strings in the themes and plugins I've built and add them to WPML. The site is under development and has limited visibility to the outside world.

Symptoms:
When I click the scan button in WPML, it never finishes. Last time it ran for several days without effect, and now it's not even listing the files anymore.

Questions:
Is the issue a bug, a misconfiguration, or a connection problem due to limited site visibility?

March 12, 2025 at 1:03 pm #16807193

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

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

While one of my teammates handles your ticket, I will provide you with initial debugging steps.

There is probably an error in the PHP code that your site runs. First, you need to see what the errors are. Guessing what might be the problem and trying different solutions may lead to even more trouble. The first step is to enable debugging. You can add a few lines to the site’s wp-config.php file. With the error log enabled, you will see the actual problem.

To enable it, open your wp-config.php file and look for define('WP_DEBUG', false);. Change it to:

define('WP_DEBUG', true);

To enable the error logging to a file on the server, you need to add yet one more similar line:

define( 'WP_DEBUG_LOG', true );

The errors will be saved to a debug.log file inside the /wp-content/directory.

https://wpml.org/documentation/support/debugging-wpml/

Let us know what you see after the debug mode has been enabled.

March 12, 2025 at 8:26 pm #16809187

lawrenceA-3

It's really weird, as soon as I added the DEBUG_LOG the issue was gone.

It kept working when I removed it again too.

I'll let you know if the problem returns somehow.