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.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 -
- - - - - - -

Supporter timezone: Asia/Karachi (GMT+05:00)

This topic contains 16 replies, has 0 voices.

Last updated by Waqas Bin Hasan 10 hours, 48 minutes ago.

Assisted by: Waqas Bin Hasan.

Author Posts
September 2, 2025 at 6:19 am #17364365

Philip

Background of the issue:
I am trying to add more variations to products using WooCommerce. The product detail page template was built with Elementor. Here is the link to a page where the issue can be seen: hidden link

Symptoms:
If a product has many variations, such as 108 variations, the product detail page is empty and only returns the header and footer. When I deactivate the WPML String Translations plugin, the products with many variations are displayed as expected without issues.

Questions:
Why does the product detail page become empty when there are many variations?
How can I resolve the issue with WPML String Translations causing the product detail page to not display correctly?

September 2, 2025 at 8:14 am #17364766

Waqas Bin Hasan
WPML Supporter since 05/2014

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Hi,

Thank you for contacting the support.

I can see the problem at hidden link.

However, before proceeding further can you please try the following?

Take a full backup of your site and database before proceeding. It is highly advised to try these on a dev or staging site first, so your live site isn't compromised.

1) Enable debugging in your site. See https://wpml.org/documentation/support/debugging-wpml/ for details. Once enabled, this will log the errors in the debug.log file which you can upload somewhere  (i.e. hidden link) and share the download link for investigation.
2) Deactivate all plugins except WPML, String Translation, WCML and WooCommerce.
3) Switch to a standard theme like 2024 or 2021.
4) Check for the issue if it still happens.
5) Then start activating plugins one by one while keep checking for the issue. This way you 'll be able to pinpoint a conflict when & where it starts creating the problem.
6) If after activating all plugins you see that it still works fine, then switch to your theme and see if that's causing it.

Please let me know your findings and I'll try my best to help you further on the matter.

Regards.

September 2, 2025 at 8:50 am #17364903

Philip

1. **Update All Related Plugins and Themes**
I have updated all Plugins and Themes as far as that was possible.

2. **Check and Increase WordPress/PHP Memory Limit**
It's already increased.

4. **Update Translation Tables and Troubleshoot**
I have cleared the cache, that did not resolve anything.

5. **Theme-Specific Considerations**
I use Hello Elementor Theme, however even switching to another Theme did not fix the issue.

September 2, 2025 at 9:27 am #17365054

Philip

The conflict seems to be between Elementor and WPML String Translations. If both plugins are active, the product detail page is broken. If one of the two plugins is deactivated, it works.

You can find the error_log here: hidden link

September 2, 2025 at 1:17 pm #17366293

Waqas Bin Hasan
WPML Supporter since 05/2014

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Thank you for the updates.

I see there's the following error in the log:

WordPress database error Commands out of sync; you can't run this command now for query INSERT INTO `wp_options` (`option_name`, `option_value`, `autoload`) VALUES ('action_scheduler_lock_async-request-runner', '68b6b331a54884.29552149|1756803949', 'no') made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->maybe_dispatch_async_request, ActionScheduler_OptionLock->set

This error is being thrown frequently and with different variations.

This isn't a WPML error but a database + server issue. There are 2 possible solutions:

1. Quick: Remove any inprogress jobs and make sure that you are added as translator before submitting or assigning the jobs again. See https://wpml.org/forums/topic/im-getting-a-lot-of-fatal-errors/#post-15414596.

2. Recommended: Even if #1 fixes the issue, it is stilly highly recommended to check with your service provider for a proper fix. Please see https://wpml.org/forums/topic/issue-related-to-products-and-pages-after-adding-wpml-plugin/#post-16694183 for a detailed information.

September 3, 2025 at 6:26 am #17368165

Philip

1. Quick: Remove any inprogress jobs and make sure that you are added as translator before submitting or assigning the jobs again. See https://wpml.org/forums/topic/im-getting-a-lot-of-fatal-errors/#post-15414596.

I am not assigning any jobs or translations at all. All I do is add more variations to a product, but in the default language, I did not add any translations....
The limit of variations seems to be 96, if I surpass that, the Product Detail Page breaks.

September 3, 2025 at 8:05 am #17368568

Waqas Bin Hasan
WPML Supporter since 05/2014

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Thank you for the updates.

In this case, this is a clear indication of database and server issues (i.e. resources, configs or etc). Please check with your service provider as recommended in my previous message.

September 4, 2025 at 2:54 pm #17376449

Philip

Is there a way I can exclude product variations and swatches from wpml so the issue doesn't come up in the first place? Because i could not find any issues in the database either.

September 8, 2025 at 4:55 am #17382303

Waqas Bin Hasan
WPML Supporter since 05/2014

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Thank you for the updates. Have you checked with your service provider for any server resources which may need increasing, fixing or adjusting?

However, to exclude this stuff from WPML, you can either set to not-translatable or translatable with fallback mode in WPML -> Settings -> look for Post type and taxonomy translations. And for existing stuff you'll have to delete translations also by switching to the secondary language from top admin bar and then remove translations in the relevant screens. See https://wpml.org/faq/how-to-delete-the-translation-of-a-page/ for an idea.

But before that, I'll recommend checking WPML/WCML Troubleshooting Options and see if these help in this situation.

September 8, 2025 at 9:06 am #17382824

Philip

My service provider shows no signs of heavy resource consumption. My server is only using 50% CPU max, and 25% of the available memory, so it's most likely not an issue related to that.

Its not really a page that I have to delete the translations of though, or at least I wouldn't know which one... The issue coms from the Variation Swatches not from a specific page.

I tried marking the content as not translatable, but that didn’t resolve the problem. Interestingly, when I set up a staging environment and deleted all WPML data, the issue was completely resolved. While this isn’t a viable solution for the production site, I thought this information might be valuable in helping identify a solution that can be safely applied on the live environment.

I have also tried every Troubleshooting Option - no results.

September 8, 2025 at 11:14 am #17383352

Waqas Bin Hasan
WPML Supporter since 05/2014

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Thank you for the updates.

I need to take a closer look at your site. So I request temporary access (WP-Admin and FTP), preferably to a test site where the problem has been replicated.

Your next answer will be private, to share this information safely.

Also provide detailed steps to reproduce the issue and links to pages in the admin and on the frontend.

IMPORTANT: Please take a complete backup of the site to avoid data loss. I may need to activate/deactivate plugins also.

See https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ for details on privacy and security.

P.S.: If you don't see the section for providing access information, do not write in the message box or the information may appear as public.

September 9, 2025 at 4:52 am #17385466

Waqas Bin Hasan
WPML Supporter since 05/2014

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Thank you for the access and the details. I am working on this and 'll get back to you as soon as I find something or have a solution.

September 9, 2025 at 5:42 am #17385518

Waqas Bin Hasan
WPML Supporter since 05/2014

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Thank you for your patience and cooperation.

I've tried to reproduce the issue in your staging site but looks like it is working just fine. I tried with only WPML, String Translation, WCML, WooCommerce, Elementor and Elementor Pro, while using Hello Elementor theme.

Please hidden link">watch my screen recording for an understanding about what I did and how I checked it.

Only thing I found the translations were available but not linked, thus showing + icon for Italian as you'll notice in the video. However, still the translations were incomplete. I'm not sure if in your production site you've completed the translations but here it looked like these weren't. So simply updating the product without making any change and then updating the translation worked for me.

Other than that, there's a deprecated notice in debug log, which is just a notice and does not impact the functioning. This should also go away once you update WPML plugins to the latest versions (released in previous week).

Anyways, if you think I'm missing something to reproduce the issue, I'd appreciate if you can write down the exact steps to reproduce the problem - I'll try my best again.

September 9, 2025 at 6:53 am #17385641

Philip

Thank you very much for your reply and efforts!

I noticed that the "Variation Swatches for WooCommerce" plugin was also deactivated. As far as I understand, this is the actual cause of the issue with WPML String Translations. When the plugin is disabled, the product detail page works correctly — but since I do need this plugin for my site, deactivating it isn’t a viable solution.

Although it’s not yet implemented on our live environment, we are actively working on it, so the plugin is essential.

Could you please reactivate "Variation Swatches for WooCommerce" so you can see the issue in action and hopefully help me resolve it?

Thank you!

September 9, 2025 at 10:23 am #17386610

Waqas Bin Hasan
WPML Supporter since 05/2014

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Thank you for your patience and cooperation.

I checked further and looks like the issue isn't entirely coming from Variation Swatches for WooCommerce (by CartFlows). However, this plugin isn't on our compatibility list and apparently you should check with their support.

But, there are some suspects which I believe aren't entirely on the said plugin.

For example, I can see variations with product details when I deactivate one of the following plugins:

- Elementor Pro
- Variation Swatches for WooCommerce
- WPML String Translation

There are no errors in debug log and I'm also not able to determine the exact reason.

Elementor Pro is outdated and I can't update it without a valid license. So as next steps, can you please check, confirm and let me know about the following?

- Update Elementor Pro with a license so I can edit and check the related templates. Currently it seems to not load properly.
- Which template and elementor widget(s) are being used for this part of the product detail? As per my understanding it is "Produkt Detail" template, right?
- Try without some advanced or pro elements, like a simple base template or even without a template to create a product detail page (also showing variations), and see if it works?

Based on these, I'll check further and 'll escalate the issue to our 2nd tier team as well. So we can finally understand if issue is really coming from WPML or from somewhere else.