Background of the issue:
In the past, I attempted to use WPML to translate the site hidden link, into multiple languages. However, it was unsuccessful due to high resource usage and random translation order. The site has over 25,000 posts. I want to try again with one language initially.
Symptoms:
WPML previously translated posts randomly and not the newest ones first all this together with resource issues.
Questions:
Is it possible for the automatic translation to start with the newest posts first and the posts that are in the queue for future publishing?
Thank you for contacting WPML support. While you wait for one of my colleagues to take this ticket and work on it, let me provide you with the first debugging steps or see if I can help with the issue quickly.
Please ensure that the Translate Everything option is unselected. This way, you can determine what to send to the automatic translation in WPML -> Translation Management.
Hello Itamar,
Thank you for your reply.
The thing is that I want the translate everything option to be active. I just would like that it follows some (logical) rules like translating the future and most actual posts first...
With Translate Everything, you cannot determine the order in which translation jobs will be sent for automatic translation. However, you can set the old posts/pages (the ones you don't want to translate automatically yet) to the draft status. In this case, when the option 'Don't translate drafts. Only translate when I publish content.' is selected (default), your old posts pages will not be sent for translation when Translate Everything is active. This option is located in WPML -> Settings -> Automatic Translation -> 'Do you want to translate drafts automatically?'. Please see the attached screenshot.
Nevertheless, if you want to keep the old posts or pages public, this is not an option for you. In this case, what I already suggested in my first post is relevant. Use the Translation Management dashboard to select what you want to send to be translated automatically. Please see the attached screenshot.
Please let me know if you have any further questions.
Well, I am not happy with the proposed "solutions". I want to have full automatic translations and for sure I don't want to set any posts to draft.
Maybe that is something to give as feedback to the dev team: give the ability to have some rules applying for the automatic translations.
Before submitting your feature request to our second-tier supporters, I reviewed this ticket again. However, I'm not sure what feature you are suggesting. Therefore, I'm unsure what you are suggesting.
You wrote: "give the ability to have some rules applying for the automatic translations."
And before that, you wrote: "The thing is that I want the translate everything option to be active. I just would like that it follows some (logical) rules like translating the future and most actual posts first..."
The following points may clarify the matter.
A. When enabling the Translate Everything option, you can select whether to have your entire site translated or only future content. One of these options must be selected when activating the Translate Everything option. Please see the attached screenshot set-uptranslate-everything.jpg. So, if you choose the second option only to translate future content, any existing content will not get translated. Later, you can change it to the option to translate the entire site.
B. You can also exlude any port type from being translated. You do it in WPML -> Settings -> Post Types Translation. Please see the attached screenshot dont-translate-posts.jpg. Any post type you set to 'Not translatable' will not be sent to automatic translation. Later, you can change it.
C. No matter how big your site is, the automatic translation of existing content (your mentioned 25,000 posts) will be completed somewhere between a few minutes and a couple of hours. So I don't see the point of setting a priority on what to translate first.
Please let me know if the above clarifications help you to achieve what you want. Otherwise, please provide more details about your feature request so I can submit it to our second-tier supporters.
