Problem: You are unable to find where to sync product categories hierarchy among languages after the latest WPML update. Solution: We recommend you to synchronize your product categories hierarchy at WPML > Taxonomy Translation. For detailed guidance on translating WordPress taxonomies, please visit our documentation: Translating Post Categories and Custom Taxonomies.
If this solution does not resolve your issue or seems outdated, 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client assigned credits to their site but cannot use them in the WPML backend. Solution: If you're experiencing issues with using assigned credits on your WPML site, we recommend you unregister and then re-register your WPML. Here are the steps to follow: 1. Log in to your WPML.org account and navigate to the Sites page. 2. Delete the existing site key. 3. Log in to your site, go to the Dashboard >> Plugins >> Add New > Commercial tab and click the Unregister WPML from this site link if it exists. 4. Click the Register WPML link. 5. Click the Get a key for this site link. This will generate a new key for your site, and you can assign the credits using that popup. 6. Copy the new key, paste it back into the input box, and press the Register button.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket for further assistance at WPML support forum.
Problem: The client wants to set the custom field _bubble_new to COPY in all languages for the NEW Bubble created by the FLATSOME theme, but cannot find the slug _bubble_new in the Custom fields in WPML settings. Solution: We tested and found that the issue might be due to the way Flatsome handles these fields. The field _bubble_new is managed within the "wc_productdata_options" field, which is set to "Translate" by default. This setting should ensure that the value is copied correctly across translations without needing to manually set it to COPY. We recommend checking this behavior in your environment to confirm.
If this solution does not resolve your issue or seems outdated, please visit our known issues page and ensure you have the latest versions of themes and plugins installed. If further assistance is needed, do not hesitate to open a new support ticket.
Problem: The client is trying to set an alternative payment method for Credit Card Stripe for the UK version of their website. They have it working on another website but encounter a 'Not yet supported' notice when configuring it for the new site in WooCommerce Multilingual and Multicurrency options. Solution: We recommended the client to ensure that the new site is configured to use Stripe as the credit card option, similar to the other site. The client should review both sites' configurations to confirm that Stripe is activated and properly set up on the new site. If the issue persists, it might be due to a piece of code in the functions.php file that was intended to hide some payment methods on the front end but inadvertently hid them in the backend—adding an
if (is_admin())
condition might resolve this issue.
If this solution does not resolve the issue or seems irrelevant due to updates or differences in your 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client needed to display the language in which an order was made on the backend order page, to distinguish orders for products with the same name across different languages. Solution: We explained that by default, the order page displays in the primary language and that the admin interface is designed to consistently display in the selected language for ease of management. We acknowledged that the specific feature requested is not currently available and would require custom development. We offered to submit a feature request for the development team to consider. Additionally, we suggested that if the feature is urgently needed, the client could consult with one of our certified partners for custom work. Relevant links for finding a certified partner and guidelines for seeking consulting help were provided:
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If so, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please do not hesitate to open a new support ticket. For further assistance, you can reach out to us on the WPML support forum.
Problem: The client was unable to limit the countries where the Stripe payment method could be accessed at checkout. After selecting the desired countries and hitting the SAVE button on the Stripe settings page, the changes were not being saved. Upon refreshing the page, the payment method was still available in all countries. Solution: We acknowledged an existing issue with the Country Availability option when using Stripe with WooCommerce. We recommended the client to follow the documentation provided to apply the necessary code to address this issue. The documentation can be found here: https://wpml.org/errata/woocommerce-stripe-payment-gateway-country-availability-changes-are-not-saved/
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please open a new support ticket with us.
