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.

Tagged: 

This topic contains 6 replies, has 0 voices.

Last updated by Itamar 3 days, 23 hours ago.

Assisted by: Itamar.

Author Posts
February 8, 2026 at 3:35 pm

fredrikS-7

Need help to solve the problem

February 8, 2026 at 5:00 pm #17803256

Itamar
WPML Supporter since 02/2016

Languages: English (English )

Timezone: Asia/Jerusalem (GMT+02:00)

Hi, and thanks for the access details.

I accessed your site and found it without any plugins installed. Please see the attached screenshot. It seems you deleted the entire contents of the /wp-content/plugins/ folder. Naturaly in this situation, I cannot investigate the performance issue. Please restore your site to its normal state and let me know when it is done.

Thanks,
Itamar.

2026-02-08_18-58-27.jpg
February 8, 2026 at 6:05 pm #17803299

fredrikS-7

Hi,

It was just renamed to plugins-hold.

I renamed it back to just plugins.

Now you can see everything again.

February 8, 2026 at 6:06 pm #17803302

fredrikS-7

It was because the site was loading so slow and I had to go for a while. Still had to give you credentials so you could work. Just missed to rename it. - Sorry.

February 9, 2026 at 10:05 am #17804346

Itamar
WPML Supporter since 02/2016

Languages: English (English )

Timezone: Asia/Jerusalem (GMT+02:00)

Hi,

Thanks for sorting this out.

When I accessed your site now, I noticed that WPML and its add-ons are inactive. Nevertheless the site still loads slow. The frontend and backend loaded in around 20 seconds. I believe there is another cause of the performance problem on your site, besides WPML. I assume that when WPML is active, the site loads even more slowly. But this would be the case when activating any other plugin. I connected to your site with FTP to check the debug.log file in the /wp-content/ folder. And I discovered it is huge. Its size is 1.14 gigabyte and my code editor can't open it. Please see the attached screenshot. I assume that the errors in the debug.log file could tell us a lot about the performance issue. Therefore, please approve the following.

A. Allow me to delete the debug.log, so WordPress will create a new file which I can work with.
B. Allow me to deactivate plugins and switch the theme to a default WordPress theme.

Do you allow me to proceed with this?

**** Important! Please make a full site backup (files and DB) before you proceed with those steps****

Regards,
Itamar.

2026-02-09_11-52-46.jpg
February 11, 2026 at 8:49 am #17811750

fredrikS-7

Yes please, just go ahead.
I was waiting for reply via e-mail therefore slow response.

I could also see that Uncode made an update and they had a problem with Woocommerce "fatal error" - maybe that problem was affecting the site.

Anyway - the site runs more smooth now - but you can delete any log - I hardly ever have time to read them.

Even if site runs smooth it can be good to see if there still are any problems.

Many Thanks!

February 11, 2026 at 9:54 am #17811996

Itamar
WPML Supporter since 02/2016

Languages: English (English )

Timezone: Asia/Jerusalem (GMT+02:00)

Hi,

I'm glad that the site runs smoothly now!

I assume the problem was not directly caused by WPML, but rather by the Uncode and WooCommerce issue you mentioned.

In any case, I went ahead and deleted the huge debug.log. Then I navigated between some backend and frontend pages and checked the newly created debug.log. In it, I only found the following error, which mentions WPML.

WordPress database error Commands out of sync; you can't run this command now for query SHOW FULL COLUMNS FROM `wp_options` made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, WPML_Notices->save_to_option, update_option

I then went to WPML -> Support -> Troubleshooting (link), and clicked the following options.

- 'Clear the cache in WPML'

- 'Remove ghost entries from the translation tables'

- 'Fix element_type collation'

- 'Fix WPML tables collation'

- 'Cleanup and optimize string tables'

This seems to have cleared the error, because I revisited some backend and frontend pages, and the error I mentioned no longer appears.

I've noticed that the debug.log on your site grows very quickly. This can, in itself, cause your server's free space to shrink, which can lead to performance issues. My general suggestion to you is to disable writing to debug.log and only enable it when you need it. You can do it by changing the following in the wp-config.php file.
Look for this code:

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );

And change it to 'false' like this:

// Enable WP_DEBUG mode
define( 'WP_DEBUG', false );
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', false );

In conclusion, I'd say the following.

1. Your site runs smoothly now with no perfromance issue.

2. The performance issue was probably not because of WPML.

3. One error that was related to WPML was fixed by applying some troubleshooting options.

4. It would be better to disable the WordPress debug.log and only activate it when needed.

I'd be thankful if you mark this ticket as resolved.

Best Regards,
Itamar.