Skip Navigation

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.

No supporters are available to work today on this forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 12:00 – 14:00 12:00 – 14:00 12:00 – 14:00 12:00 – 14:00 12:00 – 14:00 -
- 17:00 – 21:00 17:00 – 21:00 17:00 – 21:00 17:00 – 21:00 17:00 – 21:00 -

Supporter timezone: Europe/Vienna (GMT+01:00)

This topic contains 25 replies, has 3 voices.

Last updated by Bigul 1 month ago.

Assisted by: Bigul.

Author Posts
September 30, 2024 at 10:58 am #16235646

Shekhar Bhandari
Supporter

Languages: English (English )

Timezone: Asia/Kathmandu (GMT+05:45)

Hello there,

Yes, you can create a new staging site, I agree with updating all products at once, you can try it with 100 at a time.

Look forward to your reply.

Thanks

September 30, 2024 at 12:12 pm #16236048

kasperG

Even updating 100 products crashes the server. See attached. Going lower means manually updating the products more than 40 times. This is without having any reassurance that this will fix the issue. The error hasn't even been located. It feels like I've been sent on a wild goose chase here.
Is there any way to get to the bottom of the issue here before trying out possible fixes which will take me hours of work?

Screenshot 2024-09-30 at 14.08.17.png
September 30, 2024 at 12:42 pm #16236180

Shekhar Bhandari
Supporter

Languages: English (English )

Timezone: Asia/Kathmandu (GMT+05:45)

Hello there,

I understand your concern but to fix the issue we would need to find a way to reproduce which in this case is random, making it hard to debug properly.

I am asking for a second opinion from our 2nd tier to see if there is any other options rather then updating the products manually.

Thanks

September 30, 2024 at 12:46 pm #16236185

kasperG

Hi

sure, but updating the products will not lead to re-produce the error. It will only fix it. As I wrote earlier products go from OK to not in stock and a price of 0. I cannot see how bulk updating all products in the shop will help locate the error. Not sure what the end goal is with updating the products. Eventually, some will go back to not being on stock, and then we're at the same point, as we are now.

Let me know if you have any updates.

October 1, 2024 at 7:36 am #16238707

kasperG

Hi again,

Is there any way we can escalate this issue? We’re losing money because our customers can’t purchase our products. I’d really appreciate any help you can provide.

October 1, 2024 at 7:38 am #16238710

Shekhar Bhandari
Supporter

Languages: English (English )

Timezone: Asia/Kathmandu (GMT+05:45)

Hello there,

I have already escalated this issue to our 2nd tiers for further feedback and I am waiting for there response. I will update you as soon as I will receive any further feedback from them.

Thanks

October 1, 2024 at 9:10 am #16239153

Shekhar Bhandari
Supporter

Languages: English (English )

Timezone: Asia/Kathmandu (GMT+05:45)

Hi,

I’ve just received feedback from our second-tier support team, and they also pointed out that identifying the root cause of this issue is difficult due to its random occurrence.

They also mentioned that stock counts may not have synchronized correctly, especially if there were server outages (Apache, PHP, or database), or if WCML was temporarily deactivated. This could have led to stock discrepancies for purchases made during that time.

We understand this process may take time, and I agree that manually updating products in batches is not ideal. However, at this moment, it’s the only workaround available.

Looking forward to your response.

Thanks,

October 3, 2024 at 9:57 am #16248900

kasperG

The issue seems to be related cached transients in Woocommerce. We're investigating further. Please keep this ticket open.

October 3, 2024 at 11:51 am #16249559

Shekhar Bhandari
Supporter

Languages: English (English )

Timezone: Asia/Kathmandu (GMT+05:45)

Sure.

October 7, 2024 at 1:42 pm #16261800

kasperG

We've located the problem to a transient WooCommerce uses in the product when it's calling WC_Product::get_children() for the translated product. The transient is called "_transient_wc_product_children_{product_id}", and it is out of sync for the product with the incorrect price and stock.

The content of the transient is "a:2:{s:3:"all";a:0:{}s:7:"visible";a:0:{}}".

The issue can be solved by saving the product. The transient is then invalidated and thus flushed.

I hope you can escalate this issue further up the chain.

You'll probably not be able to identify any product on either the production or the staging site as we've set up a script that checks the transients and re-saves the products in case there is an issue.

October 9, 2024 at 6:50 am #16268190

Bigul
Supporter

Languages: English (English )

Timezone: Europe/Vienna (GMT+01:00)

Hello,

I am Bigul from the WPML support team. Shekhar is on vacation now, so I am taking care of this ticket. I hope it will be okay for you.

Thank you for the details. One doubt about the following. Are you calling the function to check the transients in the child theme? Please describe little more information about it.

You'll probably not be able to identify any product on either the production or the staging site as we've set up a script that checks the transients and re-saves the products in case there is an issue.

--
Thanks!

Bigul

October 16, 2024 at 7:52 am #16293835

kasperG

Hi,
I believe there’s plenty of information to work with. Let me remind you, this is information we gathered ourselves. I think it’s time for you to do your own detective work now.

October 16, 2024 at 10:18 am #16294762

Bigul
Supporter

Languages: English (English )

Timezone: Europe/Vienna (GMT+01:00)

Hello,

Thank you for the feedback. I have shared it with our second-tier team for further checking. We will get back to you as soon as possible. Please wait.

--
Thanks!

Bigul

October 16, 2024 at 3:28 pm #16296637

Bigul
Supporter

Languages: English (English )

Timezone: Europe/Vienna (GMT+01:00)

Hello,

We tested the issue and could only recreate it by manually setting these values in the transient like the following. Please check the attched iamge.

a:2:{s:3:"all";a:0:{}s:7:"visible";a:0:{}}

We tried a variable product with two variations. When we edit the transient, nothing appears for the translation. However, if we edit the product translation using either the Classic or Advanced Translation Editor, the transient updates correctly without any issues. We can consider using the following code to clear the transient when a translation job is completed:

add_filter('wpml_pro_translation_completed', 'clear_product_children_transient', 10, 1);

function clear_product_children_transient($product_id) {
    $transient_key = '_transient_wc_product_children_' . $product_id;
    delete_transient($transient_key);
}

While this solution can clear the transient, it is usually not needed since the transient is removed when saving the translation. But the main question remains: what triggers the transient to have empty values? This will help solve the root issue, as the current approach only addresses the symptoms. As a workaround, the "Transient Cleaner" plugin or WooCommerce troubleshooting tools can be used to resolve the problem temporarily.

Please note that when the transient has these values, it prevents the parent product from displaying variations. This is unrelated to stock availability, despite the message saying, "This product is currently out of stock and unavailable," which is a general WooCommerce alert.

We noticed that the staging site is currently not working and shows a fatal error: hidden link. Have there been any recent changes made to the staging site? Also, the SFTP credentials are not working now. Please check.

We are eager to help resolve this issue, but we need your assistance. Could you please share more details about the steps you are taking or any other relevant information that could help us understand the problem better? Your input will be crucial in helping us troubleshoot. Once we have this information, we will be able to replicate the issue on a fresh installation, which will greatly assist in finding a solution.

Thank you for your kind understanding and cooperation.

--
Thanks!

Bigul

image.png

The topic ‘[Closed] Woocommerce is not in stock in second language’ is closed to new replies.