Problem: You are experiencing issues with your logo not displaying correctly in the translated version of your site. Specifically, the logo appears black instead of transparent in German, and the translation pen loads indefinitely when changes are made. Solution: We applied custom CSS to address the logo display issue. Please add the following CSS code to your site by navigating to WP > Appearance > Customize > Additional CSS:
If this solution does not resolve your issue or seems outdated, we 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.
The client is experiencing unusually long delays in automatic translations using the WPML plugin on a custom theme site. They are concerned about whether their theme's development is compatible with WPML.
Solution:
We recommend the following steps to diagnose and potentially resolve the issue:
1) Ensure a full site backup is taken. 2) Temporarily switch to the default Twenty Twenty-Five theme. 3) Attempt to translate a page using the Advanced Translation Editor and check for completion. 4) If the translation completes successfully with the default theme, it indicates that the issue may be related to the custom theme.
For the custom theme to work properly with WPML:
1) Ensure custom blocks are registered using
1
register_block_type()
. 2) Add a
1
wpml-config.xml
file to the theme folder to specify which block attributes should be translatable. Example:
1
2
3
4
5
6
7
8
<wpml-config>
<gutenberg-blocks>
<block type="yourtheme/hero-block">
<translate>attributes/title</translate>
<translate>attributes/text</translate>
</block>
</gutenberg-blocks>
</wpml-config>
3) Translate template parts or patterns from WPML → Translation Management. 4) Use translation functions in theme files and ensure the theme's text domain is loaded. 5) Set pages and custom post types to 'Translatable' in WPML → Settings → Post Types Translation.
For further guidance, consult the following documentation:
If these steps do not resolve the issue or if the solution seems outdated or irrelevant, we highly recommend opening a new support ticket. Also, check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins.
Problem: The client wants to prevent WPML from automatically creating strings for the Blog Title and Tagline every time the General Settings page is saved. These strings are shared across sites but should remain unique and untranslated for each site. Despite attempts to delete these strings from the WPML interface, they reappear after settings are saved. Solution: We explained that WPML does not provide a hook to prevent the registration of default WordPress strings like Blog Title and Tagline in the WPML String Translation. These strings are automatically saved once option values are updated in WordPress. The client can delete the strings at WPML > String Translation or adjust their translation as needed. Additionally, the actions triggered when these options are updated are:
For more details on WPML hooks, visit WPML Hooks Reference. Please note, we do not support custom code modifications and cannot take responsibility for issues arising from custom implementations. For our support policy, see WPML Support Policy.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest checking related known issues at WPML 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.
Problema: El cliente está intentando eliminar el slug '/portfolio-item/' de su sitio web multilingüe y ha añadido código personalizado en el archivo functions.php para modificar los permalinks y ajustar el selector de idioma de WPML. Sin embargo, el selector de idioma no funciona correctamente y elimina el prefijo '/ca/' para el idioma catalán, resultando en un error 404. Solución: 1. Modificar el código para ajustar el selector de idioma de WPML. Aquí está el código recomendado que no hemos probado, pero podría ser útil:
Si la solución propuesta no resuelve el problema o si el código es irrelevante debido a actualizaciones o diferencias en la configuración, recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos y confirmar que se han instalado las últimas versiones de los temas y plugins. Si necesita asistencia adicional, puede contactar a nuestros partners certificados en https://wpml.org/contractors/.
Problem: The client is attempting to auto-translate their entire site but encounters issues where post titles are translated, but not the content. Only some taxonomies are translated, and content on some pages is completely missed by the auto translator. Additionally, the client asked if there is a quick way to sync the translated post dates with the originals. Solution: We recommended two approaches to address the translation issues: 1. We provided a custom XML configuration to be added in WPML > Settings > Custom XML Configuration. This configuration ensures that more elements such as paragraphs, headers, and list items are translatable. Here is the XML code to use:
2. For posts that were not correctly translated, we advised manually triggering the translations. This involves editing the problematic posts, saving them, and then using the "pencil" icon in the sidebar translation option to retranslate the posts.
If these solutions do not resolve your issue or seem 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 the problem persists, please open a new support ticket.
Problem: The client is experiencing an issue where a specific URL on their site is being incorrectly redirected to a different URL, even though they are different pages. The client tried disabling WPML redirects and modifying the database and server settings, but the issue persisted. The client observed that the issue does not occur when WPML is disabled. Solution: We investigated the issue and found that the redirection problem persists even when WPML is disabled, indicating that the issue is not related to WPML. It was suggested that the problem might be due to WordPress or the server trying to guess the correct page based on similar slugs. We recommended that the client consult with their developer to explore further, possibly by using unique slugs for each page to prevent incorrect guessing by WordPress or the server. Additionally, we advised that our support for custom-coded solutions is limited, and for issues related to custom code, the client might consider hiring a contractor from https://wpml.org/contractors/.
If this solution does not resolve your issue or seems irrelevant due to being 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 https://wpml.org/forums/forum/english-support/.
Problem: The client needed to retrieve the currency list with the exchange rates for their site using WPML and was unsure which hook to use. Solution: We advised the client to access the currency list and exchange rates through the
1
_wcml_settings
option in WordPress, which is a serialized array containing WooCommerce Multilingual (WCML) settings. Specifically, the
1
currency_options
key within this array holds the necessary data. Here is a step-by-step guide on how to retrieve this information:
Please note that we do not typically provide custom code solutions. For further customization, you might need to hire an independent contractor.
If this solution does not resolve your issue or seems outdated, we 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.
Problem: The client wants to stop the 'Send me a notification email when there is something new to translate' option from being automatically enabled for new customer accounts on their WPML site. Solution: We explained that WPML does not provide a direct setting to change this default behavior. However, the client can programmatically enforce this setting for all new users by adding a specific meta key during the user account creation process. Here is a basic example of how to implement this:
This code snippet adds the wpml_block_new_email_notifications meta key with a value of 1 to the wp_usermeta table, ensuring that the email notification option is unchecked by default for new users. Please note that this solution requires testing and might need adjustments for specific use cases.
If this solution does not apply to your situation, 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 at WPML support forum.
Problem: You are using WPML with Beaver Builder and have set up separate domains for different languages. However, when you switch languages in the WP Admin panel, the 'wp-wpml_current_language' cookie does not update correctly. It shows 'en' instead of 'ja', and when switching from the English domain to the Japanese domain, two cookies with values 'en' and 'ja' appear. Solution: We have identified that this issue might be related to custom code that alters WPML's default behavior. We recommend checking any custom code that might interfere with WPML's handling of cookies. Additionally, we suggest using WPML Hooks as a possible workaround for managing cookies across different domains. You can find more information on WPML Hooks here: WPML Hooks Reference. If this solution does not resolve your issue or seems irrelevant due to being 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 further assistance is needed, please open a new support ticket at WPML Support Forum.
Problem: If you're experiencing issues with the language switcher on the mobile version of your site, such as wanting to adjust its position or remove an unwanted white bar at the bottom, we can help. Solution: We recommend inserting the following custom CSS code to adjust the language switcher's position and remove the white bar. You can add this code by navigating to WP > Appearance > Customize > Additional CSS:
Please note that this code is for educational purposes and may not be the final solution. It's meant to guide you in the right direction.
If this solution does not fully address 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: You are experiencing an issue where a hardcoded string 'Built for the New Reality' on your homepage is not displaying its French Canadian translation on the live site, despite working on the staging site. You've tried saving the page, syncing theme translations, updating the translated string in String Translation, and clearing the page cache. Solution: We noticed that WPML could not write to the
1
/wp-content/languages/wpml
folder, which prevents it from generating the .mo files necessary for displaying translations. To resolve this, please ensure that WPML has the necessary permissions to write to this folder. You can do this by following these steps: 1. Visit the WPML documentation on .mo file generation. 2. Navigate to WPML → Theme and Plugins Localization. 3. Generate the .mo files.
If this solution does not resolve your issue or seems irrelevant due to being 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 needed, please do not hesitate to open a new support ticket for further assistance at WPML support forum.
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
