Skip to content Skip to sidebar

This thread is resolved. Here is a description of the problem and solution.

Problem:
When using the All Products for Subscriptions plugin with WPML, the product category selector is empty in the secondary language dashboard, causing issues with global subscription plans across multiple languages.
Solution:
We recommend adding a custom XML configuration to ensure the category settings are translated automatically, eliminating the need for manual translation. Follow these steps:
1. Navigate to WPML → Settings → Custom XML Configuration in your WordPress dashboard.
2. Insert the following XML configuration and save:

<wpml-config>
  <admin-texts>
    <key name="wcsatt_subscribe_to_cart_categories">
      <key name="*" type="taxonomy-ids" sub-type="product_cat"></key>
    </key>
  </admin-texts>
</wpml-config>

This configuration will translate the category IDs at runtime, allowing the category dropdown to function correctly in multiple languages, even though it appears empty in the backend.

Please note that this solution might become outdated or may not apply to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If this solution does not resolve your issue, please open a new support ticket.

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 2 replies, has 0 voices.

Last updated by Dražen 3 weeks, 5 days ago.

Assisted by: Dražen.

Author Posts
January 16, 2026 at 10:44 am #17736497

bjornH-12

Using All Products for Subscriptions, you can set which product terms that the plugin should work with, which is working completly fine in the primary language, All products in the categories will be available on subscriptions according to the global plans - But switching over to the secondary, no products are available on subscription - I changed my language in the dashboard and saw that the product cat selector in the plugin was empty in the secondary language.
I selected the translated terms and saved in the secondary language, which made all the products on with the selected terms available for subscriptions in the secondary language, but this deleted the settings in the primary language and no products were available for subscriptions there anymore.

Either "wcsatt_subscribe_to_cart_categories" needs to be translatable, or you should be able to select the terms in all languages.
The only workaround I could find, has been to create manual subscription plans on all products.

Please advise how to be able to use the global plans on multiple language - Woocommerce subscriptions is a thoroughly testet and WPML compatible plugin, so I was surprised to see that this extension has this bug.

January 16, 2026 at 11:43 am #17736699

Dražen
Supporter

Languages: English (English )

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

Hello,

I have escalated the issue to our compatibility team. They will investigate further, and I will update you here as soon as I have more information to share.

Regards,
Dražen

January 20, 2026 at 7:17 am #17744709

Dražen
Supporter

Languages: English (English )

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

Hello,

Our team has reviewed this, and you can use the following workaround. With this approach, the category settings will be translated automatically, so no manual translation is required.

Workaround
Go to WPML → Settings → Custom XML Configuration in your WordPress dashboard.

Add the following XML configuration and save:

<wpml-config>
  <admin-texts>
    <key name="wcsatt_subscribe_to_cart_categories">
      <key name="*" type="taxonomy-ids" sub-type="product_cat"/>
    </key>
  </admin-texts>
</wpml-config>

This XML configuration translates the category IDs at runtime. As a result, in the backend, the category dropdown will remain empty because the original ID does not exist in the secondary language.

We will escalate this issue to the compatibility development team, who will work with the plugin author on a permanent fix for a future release.

Regards,
Drazen