Problem: The client is experiencing a white screen when trying to edit a page with Elementor, accompanied by a TypeError related to the json_decode function in the WPML plugin. The error message indicates that json_decode expects a string, but an array was given. Solution: We recommend the following steps to troubleshoot and potentially resolve the issue: 1. Perform a full backup of your site. 2. Temporarily deactivate all third-party plugins except WPML and Elementor to check for conflicts. 3. If the problem persists, provide FTP access to the staging site so we can examine the error logs for more detailed information. 4. Contact Elementor support as the issue persists even after deactivating WPML, suggesting that the problem might not be directly related to WPML.
Please note that this solution might be outdated or not applicable to your specific 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 issue persists, please open a new support ticket with us for further assistance.
Problem: You are experiencing issues with badly encoded characters when importing a glossary CSV file into WPML. Solution: 1. Initially, we identified an issue with special characters being badly encoded during the import process. We documented this problem in our errata, which you can check here. 2. We have resolved this issue, and the fix has been released to production. Please verify by importing your CSV file again to see if the problem with character encoding has been resolved.
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 here, 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.
Problem: You are trying to switch from using ACF and Crowdin for managing translations to using Elementor and automatic translation, and you want to create a glossary from existing translations to use with the automatic translation systems. However, you could not find any documentation or forum posts on how to export existing translations into a glossary CSV file. Solution: Unfortunately, directly exporting existing translations into a glossary CSV file is not possible. However, if you share translation memory between websites and the same segments repeat, the automatic translation will use translations from the memory and apply them without additional charges. We recommend checking the following documentation for more details:
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Also, 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. For further assistance, you can contact us directly at WPML support forum.
Problem: The client encountered an error related to WPML translations not being found in the database when executing SQL queries. The error message indicated that no translation entry was found for a specific element_id. Solution: 1. We suggested that the client check if the database entries have incorrect or mismatched ID assignments and delete the incorrect entry. This step often resolves such issues. 2. We provided a link to a related support forum topic for additional guidance: https://wpml.org/forums/topic/urgent-support-needed-wpml-translation-error-no-translation-entry-found/ 3. We advised ensuring that the element_id in the SQL query is set correctly, which in this case should be 2065915. 4. If the issue persists, we requested that the client provide site access securely for further investigation, ensuring that they back up the site beforehand.
Please note that this solution might be outdated or not applicable to your specific 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 continues, please open a new support ticket at WPML support forum.
We are using WPML and ACF + the glue plugin ACFML. We initially set an image field's translation configuration to be "copy". Now we would like to be able to change the image in the translated languages, so we set it to CopyOnce. Yet the post-edit interface in the translation language post-edit screen is still locked for that image field.
Solution:
1- Deactivate all plugins except these (https://prnt.sc/B8JbDb-AdM8t)
2- Select "Different fields across languages" translation mode in the following field groups
Atom : Teaser Item
Page Builder
3- Edit the (wp-content/plugins/sitepress-multilingual-cms/classes/custom-field-translation/class-wpml-copy-once-custom-field.php) file
4- Replace the following code at line 66
אנו משתמשים בקובצי Cookie כדי לייעל את האתר והשירותים שלנו. הסכמתך מאפשרת לנו לעבד נתונים כגון התנהגות גלישה. אי הסכמה עשויה להשפיע על תכונות מסוימות.
פונקציונלי
תמיד פעיל
נדרש כדי שהאתר שלנו יפעל ויתקשר בצורה נכונה.
העדפות
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
סטטיסטיקה
אנו משתמשים בהם כדי לנתח את הנתונים הסטטיסטיים של האתר שלנו. המידע שנאסף הוא אנונימי לחלוטין. האחסון או הגישה הטכנית שמשמשים באופן בלעדי לצרכים סטטיסטיים אנונימיים. ללא זימון, הסכמה וולונטרית מצד ספק שירותי האינטרנט שלך, או רשומות נוספות מצד שלישי, המידע המאוחסן או המוחזר למטרה זו בלבד לא ניתן בדרך כלל לשימוש לצורך זיהויך.
שיווק
קובצי Cookie אלה עוקבים אחר הגלישה שלך כדי לספק מודעות רלוונטיות עבורך.
