Problem: The client is experiencing issues with Offload Media, specifically duplicated entries in the database, and is unsure about the functionality of certain WPML Media Translation settings. They observed that when translating posts through the editor with specific settings untoggled, the featured images are not copied, although content images are. Solution: We explained that the behavior of media in WPML is as expected. If the 'Duplicate existing media for translated content', 'Duplicate the featured images for translated content', 'Duplicate media attachments for translations', and 'Duplicate featured images for translations' settings are not enabled, the system does not duplicate or translate these elements. Specifically, for featured images to be translated or duplicated, the relevant checkbox must be checked. Then, the images should be managed via Translation Management to ensure they are correctly assigned per language. When translating a post that includes an image within its content and the media functionality is disabled, the original image from the default language is displayed unless adjusted by other settings or filters, such as those used by some page builders.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, 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 problems persist, please open a new support ticket.
Problem: The client has migrated their content from the Classic Translation Editor to the Advanced Translation Editor (ATE) in a test environment and is considering cleaning up the database after the migration, despite the content being mostly individually edited. Solution: We recommend continuing to use one editor, the Advanced Translation Editor, for all site content to maintain consistency and ease of use for translators. After switching from the Classic Translation Editor to the Advanced Translation Editor, existing translations will still be visible on the frontend. However, these translations might be completely or partially missing when opening the post in the Advanced Translation Editor. For more details, you can visit Switching from Classic to Advanced Translation Editor. Additionally, there is no need for a database cleanup after moving to the new editor, even if the content was initially translated using the Classic Editor.
If this solution does not resolve your issue or seems outdated, please 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. We highly recommend opening a new support ticket if needed.
Problem: The client is developing a site and using WPML to streamline the translation workflow. They have a custom field to set a menu on a specific post type and want the same menu on translated pages without needing to translate the menu name or set it manually each time. They are experiencing issues with unnecessary translation requests for some values. Solution: We explained that there isn't a specific option to control this behavior directly when it's set to 2, as the ACF translation is activated regardless of the input provided. We suggested using the "Different fields across languages" option, which allows translating the input method directly as a string. For more details, see the documentation on translating ACF field labels with WPML.
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 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.
Problem: The client was trying to set up automatic renewal for their WPML Agency subscription but was concerned about being charged a higher fee than expected. Solution: We informed the client that they have a special Agency subscription pricing of $59/year, which is a loyalty offer and the lowest possible renewal fee. This offer is no longer available for new contracts, and we advised the client to keep automatic renewals enabled to maintain this special rate. If the subscription is canceled, the client would have to renew at the current rates. Upon further communication, it appeared that the client had accidentally canceled their subscription. We asked the client to try re-enabling automatic renewals and informed them that we would check if the renewal at $59 was processed correctly. After the client followed the instructions, we confirmed that the payment went through at the previous pricing. We apologized for any inconvenience caused. If the solution provided here is not relevant to your case, either because it's outdated or it doesn't apply to your situation, we recommend that you 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. If you still need assistance, please open a new support ticket.
Problème :
Le client rencontre des problèmes de cohérence lors de la mise à jour de WPML et de ses dépendances via le CLI WordPress. Les mises à jour ne semblent pas toujours disponibles de manière cohérente entre les différents environnements enregistrés.
Solution :
Nous avons identifié que le problème n'est pas un bug mais un souci de documentation concernant la constante OTGS_DISABLE_AUTO_UPDATES. Cette constante, lorsqu'elle est définie sur true, empêche WPML de rechercher des mises à jour automatiquement. Il faut les rechercher manuellement (d'où les incohérences entre sites).
Pour résoudre ce problème :
1. Supprimez la constante OTGS_DISABLE_AUTO_UPDATES pour permettre à WPML de vérifier les mises à jour.
2. Si vous souhaitez désactiver les mises à jour automatiques, utilisez la fonction de WordPress en ajustant les paramètres depuis la page des plugins.
Si cette solution ne s'applique pas à votre cas, car elle pourrait être obsolète ou ne pas correspondre à votre problème, nous vous recommandons de vérifier les problèmes connus, de confirmer que vous avez installé les dernières versions des thèmes et plugins, et si nécessaire, d'ouvrir un nouveau ticket de support sur notre forum d'assistance.
Utilizamos cookies para optimizar nuestro sitio web y nuestros servicios. Su consentimiento nos permite procesar datos como el comportamiento de navegación. No dar su consentimiento puede afectar a algunas funciones.
Funcional
Siempre activo
Necesario para que nuestro sitio web funcione y se comunique correctamente.
Preferencias
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Estadísticas
Las utilizamos para analizar las estadísticas de nuestro sitio. La información recopilada es totalmente anónima.El almacenamiento o acceso técnico que se utiliza exclusivamente con fines estadísticos anónimos. Sin una citación, el cumplimiento voluntario por parte de su proveedor de servicios de Internet, u otros registros de terceros, la información almacenada o recuperada solo para este propósito generalmente no puede usarse para identificarlo.
Marketing
Estas cookies rastrean su navegación para proporcionar anuncios relevantes para usted.
