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: America/Lima (GMT-05:00)

Tagged: 

This topic contains 11 replies, has 0 voices.

Last updated by Andreas W. 2 hours, 55 minutes ago.

Assisted by: Andreas W..

Author Posts
January 18, 2026 at 12:56 am #17739649

willJ-2

Hello, Ive have successfully translated most of the site from English to Dutch, however I can seem to get the subscription products to show at all on the translated version?

The site is running WooCommerce Subscriptions and All Products for WooCommerce Subscriptions. The Subscription options show up on the english version but not the dutch translated version? Ive attached two screenshots to help show you what I mean.

Am I missing something or doing something wrong?

Really appreciate your help,
thanks - Will

January 18, 2026 at 3:10 am #17739707

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hello,

The issue might be related to a specific custom field setting at WPML > Settings > Custom Field Translation. Revise the available fields related to product subscription.

Set any settings or numeric fields to "Copy" and set fields that require text translation to "Translate".

After that, update the product's translation.

Guide: https://wpml.org/documentation/getting-started-guide/translating-custom-fields/

If this does not solve the issue, it would be very helpful if you could send us the WPML troubleshooting information.

More information can be found here:
https://wpml.org/de/faq/provide-debug-information-faster-support/

Also, please take note that there are currently the following known issues:
https://wpml.org/documentation/woocommerce-extensions-compatibility/translating-woocommerce-subscriptions-woocommerce-multilingual/#known-issues

Best regards
Andreas

January 20, 2026 at 12:53 pm #17746513

willJ-2

Thanks for your speedy reply I didn't see that you have replied already.

Ive attached the debug info above.

I have looked through the Custom Field Translation but im not really too sure what im looking for.

also your final point of 'After that, update the product's translation.'
Is there a way of doing that without replacing the already translated text for the products that had been checked?

Thanks for your help.

January 20, 2026 at 1:20 pm #17746623

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Thank you for your cooperation!

The settings look fine. It might be better if I take a closer look at this.

I'd like to request temporary access (wp-admin and FTP) to the website to investigate the issue further.

You'll find the necessary fields below the comment section if you log in to leave the next reply. The information you provide will be private, meaning only you and I will be able to see and access it.

IMPORTANT
Please be sure to create a backup of the website and database before granting us access.

If you don't see the "wp-admin / FTP" fields, your login credentials for the post and website will be set to "PUBLIC." Do NOT publish the information unless you see the required wp-admin / FTP fields.

I may need to install a plugin called "All In One WP Migration" to create a copy of the website on which I can investigate the problem more thoroughly.

I would also be very grateful if you could provide a staging site on your server for this purpose.

If you have any questions about creating such a staging site, please contact your hosting provider. Please ensure that WPML is also registered on this staging site at https://wpml.org/de/account/websites/.

If you are unable to provide such a copy of the website for testing, please let me know on this ticket.

The private reply form looks like this:
hidden link

When replying again, click "I still need assistance".

Video:
hidden link

Please note that we are required to request this information individually on each ticket. We are not permitted to access any login information that was not specifically provided in the private reply form for this ticket.

January 27, 2026 at 5:24 pm #17768485

willJ-2

Thanks for getting back to me. Sorry for the delay in my response.

I will create a staging site on the same server as the main site this week and get back to you with the details you require to investigate.

Thanks again.

January 27, 2026 at 6:51 pm #17768720

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Thank you for your cooperation!

The private reply form is enabled again.

February 5, 2026 at 8:40 pm #17797724

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hello,

It has been a week since I requested access to your site to investigate the issue.

Could you please confirm if you still need my assistance?

I would be glad to help.

Best regards
Andreas

February 12, 2026 at 9:49 am #17815722

willJ-2

Sorry for the delay, I now have a staging site setup ready for your help again please.

Where should I add the dev site login details for you?

February 12, 2026 at 2:19 pm #17817364

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Thank you for your cooperation!

Please use the private reply form, which looks like this:
hidden link

When replying again, click "I still need assistance".

Video:
hidden link

February 12, 2026 at 11:44 pm #17819054

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

The problem is the translation of at least one string:

"All Products for WooCommerce Subscriptions require at least PHP %1$s. Learn how to update PHP"

It is translated to:

Voor alle producten in WooCommerce-abonnementen is minimaal PHP %1$s vereist. Leer hoe u PHP kunt bijwerken .

Using %2%24s inside the translation is invalid and causes an error. Those placeholders need to be identical in all languages.

This seems to have occurred on all href attributes for anchor elements, like:

<a href="%1$s">#%2$s</a>

translated into:

<a href="%1%24s">#%2$s</a>

It seems that this occurred when translating those strings automatically using the Google Translation Engine on the 17th of January.

Do you think that this issue might have occurred while translating those strings with automatic translation?

Would you mind if I test on your site if this issue is replicable? I would give some credits for testing to our account in this case.

Now, I have already tried to manually fix dozens of such translations, but once I search on String Translation for "%1$s" I get about 1300 results. It is impossible for me to verify all those strings.

Do you mind if I enable WP DEBUG on the site to get a better idea of which strings might be affected?

February 13, 2026 at 6:40 pm #17821561

willJ-2

Amazing thanks,

The string you mentioned:

"All Products for WooCommerce Subscriptions require at least PHP %1$s. Learn how to update PHP"

Sounds like its a translation from the back end of the website, somewhere within the admin areas. As far as I'm concerned this does not need to be translated and can stay in english. Would this make it easier if we kept this in English?

When you talk about testing and enabling WP DEBUG is this on the /dev version or live site?

Happy for you to do whatever you like on the /dev version.

Thanks again.

February 13, 2026 at 7:23 pm #17821622

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

I am currently working on the dev site.

Let me try to figure out how many affected strings there are; it actually makes sense to translate them. You would only need to translate backend strings if you plan to offer different admin languages for your admin users.

Further, I will run some tests and see if I can replicate this issue with Google Translate.