This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
---|---|---|---|---|---|---|
- | 8:00 – 13:00 | 9:00 – 13:00 | 9:00 – 13:00 | 8:00 – 12:00 | 8:00 – 12:00 | - |
- | 14:00 – 17:00 | 14:00 – 18:00 | 14:00 – 18:00 | 13:00 – 17:00 | 13:00 – 17:00 | - |
Supporter timezone: Europe/Zagreb (GMT+01:00)
Tagged: Documentation request
This topic contains 0 replies, has 2 voices.
Last updated by Bruno Kos 1 day, 4 hours ago.
Assisted by: Bruno Kos.
Author | Posts |
---|---|
November 18, 2024 at 10:19 am #16414066 | |
samuelR-21 |
Background of the issue: Symptoms: Questions: |
November 18, 2024 at 2:18 pm #16415253 | |
Bruno Kos Supporter
Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00) |
We are still checking this and will keep you posted. |
November 19, 2024 at 6:18 am #16417694 | |
Bruno Kos Supporter
Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00) |
To troubleshoot this problem, I'll install the Duplicator plugin and generate packages for further debugging purposes. I'll ensure to exclude all media files to maintain a minimal package size. You can find more information about the process here: [link](https://wpml.org/faq/provide-supporters-copy-site/). Please confirm if this approach is acceptable to you. |
November 21, 2024 at 12:10 pm #16428829 | |
samuelR-21 |
Hi Bruno, I didnt get any notifications on replys where made to this ticket, so i didnt even know you answered. But yes of cause, if you think this will help solve the issue. But i am almost out of time here, we have paid marketing running and need alot of stuff to be ready for black friday. Do you have a paid support option, so we can get this solved very quickly? I am happy to pay for express service. |
November 21, 2024 at 4:57 pm #16430398 | |
Bruno Kos Supporter
Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00) |
I have created a Duplicator package of your site and escalated the issue to our second-tier support team for detailed debugging. Regarding your query about paid support, I’d like to clarify that WPML support is always free of charge (comes with a license), and clients should never need to pay for support services. We are here to help with issues like these, although some cases can take longer to diagnose and resolve, particularly when interactions with other plugins are involved. For custom work or if you need assistance with tasks outside the scope of our support, we recommend https://wpml.org/contractors/. These are professionals who specialize in custom development work, but note that they do not handle bug fixing related to WPML, this is on us. |
November 22, 2024 at 10:22 am #16433173 | |
samuelR-21 |
Hi Bruno, I understand, please push this as much as you can. We are really eager to get this working. Thank you. |
November 26, 2024 at 7:23 am #16442725 | |
samuelR-21 |
Hi Bruno, are you able to get a status on this? |
November 26, 2024 at 10:39 am #16444044 | |
Bruno Kos Supporter
Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00) |
Unfortunately I don't have any news from our 2nd tier yet. |
November 27, 2024 at 10:31 am #16448614 | |
samuelR-21 |
Hi Bruno, what can we do ? Its almost black friday with our campaign and i still need to do alot of work on the site after the issue is fixed. I understand you can only do so much with the workload, but please could you escalate this further? |
November 27, 2024 at 2:15 pm #16450428 | |
Bruno Kos Supporter
Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00) |
Our 2nd tier is on this at the moment and I hope to have some news today. |
November 27, 2024 at 7:51 pm #16451546 | |
Bruno Kos Supporter
Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00) |
We have identified a discrepancy in the **"section"** field values between the original post (ID 23) and its translation (ID 2163) in the WordPress post meta table. The values are as follows: - **Original (ID 23):** `a:8:{i:0;s:4:"text";i:1;s:4:"text";i:2;s:4:"text";i:3;s:12:"image-slider";i:4;s:4:"text";i:5;s:12:"image-scroll";i:6;s:4:"text";i:7;s:13:"model-dynamic";}` - **Translation (ID 2163):** `a:8:{i:0;s:4:"text";i:1;s:4:"text";i:2;s:4:"text";i:3;s:12:"image slider";i:4;s:4:"text";i:5;s:12:"image-scroll";i:6;s:4:"text";i:7;s:13:"model-dynamic";}` The difference lies in the fourth value: - **Original:** `"image-slider"` This small variation (a missing hyphen) is critical because WordPress relies on the exact match of these field values for proper rendering and functionality. The incorrect value in the translation is causing the field to fail to display correctly. Additionally, we noticed that the **"sections"** field is set to **"Don't translate" (0)** in WPML's translation preferences. According to https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/recommended-custom-fields-translation-preferences-for-acf-and-wpml/, flexible fields should use either: - **"Copy"**: Ensures that the value is always synchronized between the original and translated posts. Having "Don't translate" set for flexible fields means any changes made to this field in the translation will be ignored, which could lead to inconsistencies like the issue observed here. To resolve the immediate issue, update the **"section"** field value for the translated post (ID 2163) to match the original format, replacing `"image slider"` with `"image-slider"`. You can do this using the SQL query such as: UPDATE wp_postmeta SET meta_value = REPLACE(meta_value, 'image slider', 'image-slider') WHERE post_id = 2163 AND meta_key = 'section'; Replace `wp_` with your actual table prefix if it’s different. Be sure to back up your database before running this query. As for the translation Preference for the "sections" Field:** After running the SQL query and updating the field's translation preference, test the translated post (ID 2163) to confirm that the field now displays as expected. You may need to resave the original. If you need further assistance with these steps, feel free to let me know! |
November 28, 2024 at 11:42 am #16454763 | |
samuelR-21 |
Hi Bruno, I changed the ** sections ** to use Copy and resaved the product with the issue, however this didnt solve the issue. The SQL query is not really a fix for the problem, its more like fixing the symptoms as i see it. Because this is happening multiple places all over the website. The query you sent fixes 1 specific place on 1 specific language. But check attached screen, these are fields missing on another language. So i need to find the root of the issue instead of doing sql queries. Also so it does not continue to happen on new content. So how do i solve it? I already changed sections to copy and resaved - what else could it be ? |
November 28, 2024 at 12:02 pm #16454852 | |
samuelR-21 |
Wrong screenshot, here is the correct one |
November 28, 2024 at 12:19 pm #16454915 | |
samuelR-21 |
Also i see that the option in ACF is set to "Same fields across languages" but how would that work for the links? Wouldnt this option result in the all links going to the original language ? I guess "Same fields across languages" would work on 99% of the content, but wouldnt it destroy the links ? As i see it it needs to be set to expert mode to work properly. Or ? |
November 28, 2024 at 12:31 pm #16454981 | |
samuelR-21 |
Additional info, when changing the ** sections ** from "Dont translate" to "Copy" - saving and then editing a product and saving. Then if you go back to WPML > Settings the value will be changed back to "Dont translate" for ** sections **. |