Problème : Le client rencontre des difficultés avec le processus de traduction automatique des chaînes de caractères dans WPML, notamment l'attribution des tâches de traduction, la validation des traductions en lot et la navigation dans l'interface de traduction. Solution : Si vous rencontrez des problèmes similaires lors de la traduction automatique des chaînes de caractères et que vous êtes le seul traducteur sur votre site, nous vous recommandons de suivre ces étapes : 1. Allez dans WPML → Traduction des chaînes de caractères. 2. Sélectionnez les chaînes à traduire automatiquement et les langues cibles. 3. Cliquez sur le bouton Traduire. 4. Rendez-vous ensuite dans WPML → Translations. 5. Cliquez sur Traduire à côté du travail de traduction avec les chaînes, qui devrait être assigné automatiquement. 6. Vous serez redirigé vers l'éditeur de traduction avancé, où les traductions automatiques sont pré-remplies pour vous. Vous pouvez les réviser et les éditer si nécessaire. Pour nous aider à comprendre et améliorer le processus, veuillez fournir une capture d'écran de l'interface et du bouton utilisé pour valider les traductions, ou enregistrer une courte vidéo du processus à l'aide d'un outil comme Loom.
Il est possible que cette solution ne soit plus pertinente, car elle pourrait être obsolète ou ne pas correspondre à votre cas. Si c'est le cas, nous vous invitons à ouvrir un nouveau ticket de support. Nous vous recommandons également de consulter les problèmes connus sur https://wpml.org/known-issues/, de vérifier la version de la correction permanente et de vous assurer que vous avez installé les dernières versions des thèmes et plugins. Si vous avez besoin d'assistance supplémentaire, n'hésitez pas à contacter notre équipe sur le forum de support WPML.
Problem: The client is working on a translation queue and expects to return to the same prefiltered/sorted list after translating an item. Instead, the filters reset, causing inefficiency and time waste. Solution: We acknowledge the inconvenience caused by the translation queue filters resetting after each translation. Currently, there is no feature to save recently applied filters on the translation queue page. We have taken note of this issue and will submit it as a feature request for consideration in future updates.
If this solution is not relevant to your case, or if it becomes outdated, we recommend opening a new support ticket. We also highly recommend checking related 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 contact us on the WPML support forum.
Problem: The client is experiencing heavy server load when running the 'Translate Link Targets' feature in WPML and is looking for a way to control or stop the process to prevent server overload.
Solution: We understand that the 'Translate Link Targets' feature can be resource-intensive. Currently, there is no direct way to adjust the speed of this process. To better handle the load, we recommend optimizing server settings such as PHP memory limit, max execution time, and database query limits, ensuring they are within the limits allowed by your hosting provider.
To stop the link scanning process, you can refresh the WPML Settings page. This will halt the process, and any links processed before the refresh will remain updated. If the process continues to run in the background after refreshing the page, we would appreciate it if you could provide details on how to replicate the issue and information about the tools used to monitor the background process.
We acknowledge that a feature to control the 'Translate Link Targets' process could be beneficial and will consider it for future updates. If you find that the solution provided here is not relevant to your case, possibly because it's outdated, or if you need further assistance, we highly recommend checking 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 open a new support ticket with us.
Problem: The client needed to synchronize the status of products, such as draft status, across multiple websites. The provided plugin only worked for products whose status changed after the plugin's installation, not for those changed before.
Solution: 1. We recommended adding the following code to the
wp-config.php
file, above the line
/* That's all, stop editing! Happy publishing. */
, to synchronize the status of the "product" post type:
2. We also suggested using the bulk edit feature to update the status of many products at once. It's important to note that the status sync will only occur when the original product is updated.
Please be aware that this solution might be irrelevant if it's outdated or not applicable to your specific case. If the provided solution does not resolve your issue, 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 you still need assistance, please do not hesitate to open a new support ticket. You can reach our support forum here.
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.
Problema: Il cliente deve sostituire il testo "Sold" con "Coming soon" per i prodotti sul sito in inglese. Soluzione: Se "Sold" è la traduzione di una stringa già esistente in italiano, il cliente deve cercare la stringa da modificare nella sezione Traduzione Stringhe di WPML. Se invece "Sold" è la stringa originale, WPML non permette la modifica delle stringhe originali, ma solo delle loro traduzioni.
Se la soluzione proposta non è applicabile al tuo caso, potrebbe essere perché è obsoleta o non adatta alla tua situazione specifica. In tal caso, ti invitiamo a aprire un nuovo ticket di supporto. Ti consigliamo inoltre di controllare la pagina dei problemi noti, verificare la versione della soluzione permanente e confermare di aver installato le ultime versioni dei temi e dei plugin.
Problem: The client needed assistance with translating BuddyBoss Group Types using WPML. Solution: 1. Navigate to WPML > Settings > Custom Field Translation and click on "Show system fields". 2. Locate the fields as shown in the provided screenshot here https://wpml.org/forums/topic/buddyboss-group-type-translation/#post-15380730 and set them to "Translate". 3. When editing a Group in the WordPress Editor, ensure the correct Group Type is selected in the right sidebar. 4. Switch the language using the top admin bar and verify that the translation uses the translated Group Type.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we encourage you to check the related known issues and confirm that you have the latest versions of themes and plugins installed. If necessary, please open a new support ticket for further assistance.
