[Closed] Too many reported errors

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.

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.

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.