Problem: The client is attempting to use a custom translation service with WPML, but it does not appear in the Translation Services list. They have set
WPML_CUSTOM_TRANSLATION_SERVICE_URL
in wp-config.php to point to their custom Translation Proxy API, which implements the WPML Translation Proxy API (JSON:API). Despite this setup, the custom service is not visible under WPML → Translation Dashboard → Translation Services. The client also noted that the “Enable other translation services” button is not visible under WPML → Support → Troubleshooting, and they do not have a Preferred Translation Service set in their wpml.org account.
Solution: We informed the client that currently, there are no plans to make custom translation services available outside of the Partner program. As alternatives, we recommended considering the following options:
Translation Hub: A centralized interface for managing translations and translators.
Automatic Translation: Built-in machine translation with flexible pay-as-you-go options.
We also mentioned that we will soon announce the PTC (Private Translation Cloud) Partnership program for Agency accounts, which will provide benefits for those accounts regarding site translations.
If this solution does not apply to your case, or if it 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.
Problem: The client needs a language switcher similar to the one on a specific website but struggles with limited customizability using standard options. They have purchased WPML and seek guidance on implementing a custom UI for the language switcher. Solution: We recommend creating a custom language switcher using WPML's PHP functions or shortcodes, which allow for full customization. You can use the wpml_active_languages filter to retrieve an array of all active languages, including their codes, URLs, and active states. This enables you to loop through these languages and apply custom classes for styling, thus gaining complete control over the HTML structure and appearance. For further guidance, please refer to the following documentation:
If this solution does not apply to your case, or if it 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. Should you need further assistance, please open a new support ticket at WPML Support Forum.
Problem: You are experiencing an issue where hreflang tags on custom post type (CPT) archives for 'event' are incorrectly pointing to the homepages instead of the translated archive pages. This issue is causing 'missing reciprocal hreflang' errors in SEO audits.
Solution: First, ensure that your CPT 'event' is set to 'Translatable' in WPML settings and that translations for the archives are properly connected. If the issue persists, the problem might be related to the theme or specific customizations in your theme's functions.php file. Here are the steps we recommend: 1. Verify the CPT registration settings. It should look like this:
2. If you are using a child theme or have custom functions that modify the query, ensure they are not affecting the hreflang output. For example, check if modifications in the functions.php like custom query filters are interfering. 3. Test with a default theme (e.g., Twenty Twenty-Five or Elementor parent) to see if the issue resolves, indicating a theme-specific problem. 4. If these steps do not resolve the issue, it might be due to limitations in the ACF or WPML integration or a need for manual adjustments in the theme or plugin settings.
This solution might be outdated or not applicable to your specific case. If the problem 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 necessary, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues with the styling of your custom language switcher, specifically with the "Hover" settings for "Other language font color" and "Other language background color" not working as expected on the frontend, this might be due to a CSS conflict or misconfiguration. The hover effect might be incorrectly applied to the current language instead of the available translation links. Solution: We recommend applying custom CSS to correct this issue. You can add the necessary CSS by navigating to WP > Appearance > Customize > Additional CSS in your WordPress dashboard.
.wpml-ls-statics-shortcode_actions a, .wpml-ls-statics-shortcode_actions .wpml-ls-sub-menu a, .wpml-ls-statics-shortcode_actions .wpml-ls-sub-menu a:link, .wpml-ls-statics-shortcode_actions li:not(.wpml-ls-current-language) .wpml-ls-link, .wpml-ls-statics-shortcode_actions li:not(.wpml-ls-current-language) .wpml-ls-link:link {
color: #000000;
background-color: #ffb536;
}
If this solution does not resolve your issue or seems irrelevant because it might be outdated or not applicable to 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: When translating your website automatically, some pages do not translate at all and do not appear in the new language. Additionally, the translate menu option is missing in the page section, unlike other websites. However, posts translate without any issues. Solution: We found a PHP error in the theme file that was causing the issue. The function was returning a WP_Error, which the theme did not validate before outputting. To resolve this, we replaced the problematic code in
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum at WPML Support Forum.
