Skip Navigation

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.

Our next available supporter will start replying to tickets in about 1.73 hours from now. Thank you for your understanding.

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: 

This topic contains 32 replies, has 2 voices.

Last updated by Bruno Kos 1 month, 1 week ago.

Assisted by: Bruno Kos.

Author Posts
September 26, 2024 at 9:35 am #16224061

alinam-2

Hello,
Started but ...
1. when willing to translate, I have image attached. I use Classic Translation Editor. Could change?
2. Could you please add a 3rd language? Easier to show case then.

That being said, I don't know what is the translation interface that you use, but there, I see things that I don't have in classic editor, like the javascript void ... and vice-versa, in classic editor, I have the images, which are not visible here.

Waiting for your feedback

Regards

translateor-sandbox.jpg
September 26, 2024 at 9:53 am #16224163

Bruno Kos
Supporter

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+01:00)

This is our Advanced Translation Editor which we recommend. Classic Translation Editor is the old translation method.

I activated classic on hidden link, but you need to create a new Item as the one you are translating already uses advanced editor.

As for adding languages, feel free to do whatever is needed in the sandbox, that's why we created so we can do various tests here.

September 26, 2024 at 11:51 am #16224804

alinam-2

Say OK

Q: how do you explain the huge difference between what is proposed to be translated between the 3 editors, here including your string translator?

The problem statement: when you open the translator for the 1st time, the image is proposed for translation. When you open it for the 2nd time (eg for another language), the image has vanished. Keeping in mind that error in log is about image, and that this generates CPU overheat.

I made 2 posts. First one, I already opened it for translation. If I re-open it for translation, image is not proposed for translation.
The 2nd is "virgin". If you open it, you will image for translation. If you open it a second time, image won't be proposed.
If you need to re-create the issue, use code editor. Copy the code of 1st article in a new one. And repeat.

For info, I have the same kind of issue on woo multilingual (other ticket). If I open, I have a version. If I re-open, another option.

Regards

September 26, 2024 at 12:57 pm #16225315

Bruno Kos
Supporter

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+01:00)

I attempted to replicate the issue, but nothing appeared in the debug logs. I also want to make sure I fully understand the entire workflow.

To move forward, could you please do the following:

- Reproduce the issue on your website.
- Record your actions using a tool like [Loom](hidden link).

This will help ensure we’re aligned on the exact steps.

Once this is done and assuming the issue persists with errors or high CPU usage, I’ll escalate the matter to our second-tier support team for further investigation.

September 26, 2024 at 1:25 pm #16225510

alinam-2

Hi,

Well, if you are a supporter, could you please help non Tech people like me (I am an artisan), and answer, rather than always shooting the ball in other fields, what is clearly preventing me from understanding.

1. how do you explain the huge difference between what is proposed to be translated between the 3 editors, classic, advanced, string?

2. What are known causes for this:
Got error 'PHP message: PHP Warning: Undefined array key 0 in /home/1164702.cloudwaysapps.com/sdfdfsd/public_html/wp-content/plugins............ key 17 in /home/1164702.cloudwaysapps.com/sdfs/public_html/wp-content/plugins/wpml-media-translation/classes/class-wpml-media-attachment-by-url-query.php on line 163', referer: hidden link

3. Why image disappear from translation to translation (re what I wrote just before)

Regards

September 27, 2024 at 5:45 am #16228070

Bruno Kos
Supporter

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+01:00)

In WPML the three different translation editors—Classic, Advanced, and String—handle content translation in different ways, which can lead to a noticeable variation in what is proposed to be translated.

### 1. **Classic Translation Editor:**
- **Approach:** The Classic Editor requires manual translation of each piece of content (e.g., posts, pages) as full, distinct entities. It doesn't break content down into smaller, reusable segments.
- **Difference in Proposed Translations:** This editor doesn’t suggest much automated or segmented translation. Instead, users must manually input translations for the whole content, so it may seem that less is "proposed" for translation in terms of automation. The whole document is presented for manual translation.

### 2. **Advanced Translation Editor (ATE):**
- **Approach:** The Advanced Translation Editor uses machine translation, translation memory, and segment-based translation for more granular control. Content is broken down into smaller translatable segments like sentences, paragraphs, or phrases.
- **Difference in Proposed Translations:** The ATE typically proposes more automated translations because it leverages machine learning and can retrieve matching translations from previous projects or external translation engines (e.g., Google Translate, DeepL). Thus, it offers a more comprehensive set of proposed translations with higher automation.

### 3. **String Translation:**
- **Approach:** String Translation is used to translate interface elements, theme/plugin strings, and small chunks of text that are typically outside the post/page content (e.g., widget text, form labels, menu items).
- **Difference in Proposed Translations:** Since it focuses on smaller, often reusable strings of text (like buttons, labels, and settings), the amount of content that it proposes for translation is quite different. String Translation might seem limited because it handles discrete snippets of text rather than long-form content, but it’s more focused on user interface elements rather than full articles or posts.

### Explanation of the Differences:
- **Granularity of Content:** Advanced Translation Editor breaks content down into smaller translatable units and suggests machine translations, which often results in more proposed translations. The Classic Editor treats entire posts or pages as a whole, leading to less granular translation suggestions. String Translation works with individual strings, leading to fewer and more focused translation suggestions.

- **Automation:** The Advanced Translation Editor leverages more automation, offering translations based on memory and machine learning, while Classic Editor relies on human translation input. String Translation can be less automated but is highly specific to technical elements.

September 27, 2024 at 5:48 am #16228071

Bruno Kos
Supporter

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+01:00)

For 2 and 3 I need hidden link recording so I could understand the workflow you have which eventually triggers the error.

We need to debug it then to understand why this error message occurs. I can't give any definite answer without debugging what's happening under the hood.

September 27, 2024 at 6:42 pm #16231138

alinam-2

Hello,

This morning, I added text in the post you know ... or should know.
Before this addition, translation was completed, at 80% via classic translator, and the last 20% roughly, made them via string, since proving faster for me. In WP / post, each of my 2 translations were marked as finished with the pencil.
After having added the text, I re-open to translate, nomore via string but via classic translator. And then, I see that what I had translated via string had gone ... in classic translator it's not ticked / approved. And I have new strings to translate ... which were already translated.
I have yet an equivalent problem with product translation ... 1/2 times, visual translator works, and 1/2 it does not. 1/2 time, woo WPML translator add p taps in original version, and 1/2 time, it does not. And 1/2 time, I have to re-validate the translation

To make it short re. our issue

1- the error I reported in linked to images
PHP Warning: Undefined array key 0 in /home/1164702.cloudwaysapps.com/sdfdfsd/public_html/wp-content/plugins............ key 17 in /home/1164702.cloudwaysapps.com/sdfs/public_html/wp-content/plugins/wpml-media-translation/classes/class-wpml-media-attachment-by-url-query.php on line 163

2- via classic translator, fact is, and is repeateadly, that an image is proposed for translation on 1st translation. But not for any folllowing or update

3- first image translation is proposed on classic editor, not advanced one. What is definitely illogical and can be qualified as bug.

Further, your answer above is a nice copy / paste, but you don't give reason re. original question. It's clearly stated line 163. you are a Tech, I am not, and you never answer to the original question

To move forward:
1. Are you able to deliver "image proposed for translation" in both advanced and classic translator, for ever. Here, you can reproduce issue on your ... site.
2. what are the known causes for this image error on line 163?

Regards

September 30, 2024 at 5:34 am #16234303

Bruno Kos
Supporter

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+01:00)

This issue occurs because WPML uses different translation systems (like the Classic Translation Editor and the String Translation interface) to manage translations, and they store translation data in separate places. When you switch between these translation methods, synchronization can sometimes break down, leading to situations like the one you're experiencing.

E.g. When you translated the last 20% using String Translation, the Classic Translator didn't get updated with that information, because it doesn't automatically sync with String Translation.

As a result, when you reopened the Classic Translator after making changes via String Translation, those parts of the content hadn't been translated and thus presented them as untranslated.

As for PHP Warning: Undefined array key 0, the error may be caused by missing or corrupt image attachments, incorrect or broken media URLs, desynchronization between the database and file system, conflicts with themes or media-handling plugins, custom code affecting media queries, inconsistent WPML Media Translation settings, incomplete media synchronization, or issues with file permissions or server configuration.

However without debugging we can't know this.

It is possible though this mixing of editor is the cause of this.

Could you please provide a Loom recording showing the workflow that triggers this error? Since it seems to be a workflow issue as described above, I'm not certain if we can fix it.

I recommend following the proper workflow, especially by using our [Advanced Translation Editor](https://wpml.org/documentation/translating-your-contents/advanced-translation-editor/). Do the errors still occur when you use only the Advanced Translation Editor? Please try with a new test page containing some text and images to see if the issue persists.

October 1, 2024 at 4:15 am #16238205

alinam-2

Hello,

What you say could make sense for the equivalent errors I have in products.
But that is not what we have here.

Note again that I am only using classic translation editor. And if I used strings on a unique post, it's was super specific (on 1 post), and because the "normal" translation was not working anymore.

Again, for me, we have to say simple. The problem which is easy to reproduce, is, if I create a post like I did on your site, the image is;
1- though it's not my problem, since I don't use it, image not proposed for translation oin advanced translator ... what is neither normal nor coherent.
- proposed only once for translation in classic editor, only for the 1st translation, and then disappear for ever ... when starting a translation on another language... and even when the 1st translation is re-open

it's necessarily of cause of bugs in databases, when the post is called by someone, be it an author, or a visitor / reader ... how is managed the "image" in original post, in language A, in language B, ....
Normally, I am supposed to even be able change the original image by others, ie have a specific image per language

OK?

Regards

October 1, 2024 at 5:03 am #16238263

Bruno Kos
Supporter

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+01:00)

Please record a video of this bug you are encountering using tool such as hidden link. Do it on your site and check if the PHP Warning: Undefined array key 0 has appeared in the logs during your translation process.

October 1, 2024 at 8:10 am #16238843

alinam-2

?
it's on your sandbox
and I explained how to reproduce
WHat is unclear?

October 1, 2024 at 9:39 am #16239224

alinam-2

Hi,
Actually checking.
Another WPML supporter is working on my stanging site.
I see now a different behavoir.
Trying to check why, I am close to it, and will revert when double-checked
Regards

October 1, 2024 at 10:53 am #16239882

alinam-2

Actually, I can't, he is using the staging site.
I've been testing whether the difference could be due to theme, since he changed it, but it's not.
But he also deactivated media translation ... that's my next thing to check when he is over.
To follow

October 1, 2024 at 12:10 pm #16240258

Bruno Kos
Supporter

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+01:00)

Sure, please keep me updated.

The topic ‘[Closed] Too many reported errors’ is closed to new replies.