I understand you want to send content (posts, pages ...) to automatic translation in bulk but it does not work. Can you please share some screenshots of the issue? What is not working in this case?
Should I use ATE per page instead?
Yes, you can translate a page manually, then click on the button "Translate automatically" in ATE. Please check this screenshot hidden link
When I had a better look at the product page = there were PROBLEMS I EXPERIENCE [did not see those at first glance]
hidden link
Which I used to translate to:
- German
- Dutch
- Spanish
There are problems with the WPML translation product page. The fields if you look [which are pre-filled]. These are product variations [attributes | and variations], are not prefilled, and do not work.
For example, in the field, [Fresh Fruits] = always Included. I think this does not go the correct way.
I'm sharing a screenshot here [You can see the difference when you select a [field] in the original English version [compared to the Translated pages in Dutch | German | Spanish].
This I would like to add to Bulk [unless you prefer to split this one], but this is a structural problem, which happened last year, and caused lots of stress at my site and support of WPML, to get this solved [keep in mind, I did not translate the Fishing Tour Page yet, so this is old and should work = also old content].
I did this on purpose [seen last problems of last year, with took far too much time from me and WPML support, so you can see the difference, and it might be easier solved:
Tour Page Cahuita Night [translated with WPML toda to DE | NL | ES] =
Tour Page Fishing [NOT TOUCHED OR CHANGED] / [BUTTON WORK WITH OLD CONTENT] =
Fishing
UK Default hidden link
Translated DE | NL | ES hidden link hidden link hidden link
Important: apparently I have not seen these were not all solved [so the old pages = often also [probably again = as these should have worked] direct [Button Links] to Default Language"-(
=
To explain something about the site [part of the site]. The website has tour pages [which link to] = product pages [of the shop].
Example A1:
Tour Page Cahuita Night Tour hidden link
links to [with three buttons], 2 visible and 1 [or more | often sliders have more slides, so also more buttons], on [each] unique tour page
Product Page Cahuita Night Tour hidden link
Default UK = of course = OK hidden link
Translated Tour Pages [TEST!]
NL [Dutch] = Problem = Button link to UK Default Language! hidden link
DE [German] Problem = Button link to UK Default Language! hidden link
ES [Spanish] Problem = Button link to UK Default Language! hidden link
This probably [reminds me of last year we “me” and “support” had the same experience, and this led to some HUGE problems.
On the other hand, there is a “loopback”, called “more information” on the Product Pages, which links:
Example A2 [loopback link “more information” = works fine!! [BUT these are no buttons !!]
From Product Page to Tour Page
Examples:
UK hidden link
DE hidden link
NL hidden link
ES hidden link
IMPORTANT NOTE
This will probably [happen with all 13 tour pages and 2 lodge pages [who link to shop] = product pages.
Example B: Tour Overview Page [this is one example = I have 6 tour / 1 lodge overview pages / which link to tour pages / which link to product pages [shop]
I translated a 1 TEST product overview page [this one has two tours – which link to these 2 tour pages [Cahuita Night Tour] and [Fishing] = I still have to translate that Fishing one] + 1 Homepage Slider with buttons that link to ALL Tours]
UK [Default] hidden link
DE [German] hidden link
ES [Spanish] hidden link
NL [Dutch] hidden link
The WPML German and Spanish Pages [Button Links] to the UK Default Language = [PROBLEM]
The WPML Dutch Page [Button Link] is OK and links to the Translated Pages.
NOTE!
This last information [I also sent while I was using the ATE, in the “support field”, with “some other problems I experienced. These are related to other issues, like partly translated links. I think you probably also have read that one.
Tomorrow I will get up early [seeing the time difference], as these are only two tests I did [and I expected these problems]; as I stated in the ATE [support mentions], I wouldn't say I like to get the same experience with the WPML translations as last year, [November / December 2022]. This was for “me” and “support Ingemar, quite a nightmare☹
So, I started with some tests, where I expected the problems; of course, I am not an expert in WPML, but with experts, it was not EASY, while it should be simple. It is a straightforward website built with DIVI Woo.
And of course, I might have forgotten things, still STEPS I have to do to make this work. But last year, this was a huge problem, also for WPML Support.
In this ticket, I will focus on one issue, translate content (posts, pages, products ...) in bulk. If you see other issues when or after translating content, please create a new topic with clear steps (and some screenshots if possible), I or my colleague will help you to check the issue.
The translation queue WPML > Translations helps you to approve pending review jobs or translate content one-by-one. It isn't possible to translate content manually in bulk as in your screenshot.
This weekend, I have been able to translate with automatic translation of most of the pages and products.
Some of the issues are resolved [ATE Translation], causing incomplete Translations. With automatic translations, it went much better [some issues are solved], but not all.
A] BIG PROBLEM WITH BUTTON LINKS and LINKS
I need an e-mail address, as I am building an Excel File, for the Button Links. This list provides an overview of all Button Links with WPML translations [NL | DE |ES].
I need, some time, as this is lots of work, and would like to provide a clear overview, so that can be solved after you receive the Button Link list.
B]
I will make for each other WPML Translation problem, a new Ticket, as concrete as possible [so it is easier, to get the overview], and to handle these, like you suggested one by one.
Regards,
TON TT
ps. After automatic translations [some problems I tried to solve with the ATE, which did not work [I left a comment about a couple of translation problems [with the ATE support form]. you probably have seen those issues = just one example [look at translation of page:
hidden link
to:
Dutch, Spanish, and German ''WPML Translations are really weird".
I even tried automatic Translation for a second time [waste of credits], you can see this particular issue live on the site [and it does not make sense, as all other volunteer pages] "are translated correctly'', al least the content is.
Problem = Ticket Homepage Slider [Button Links of Slider Homepage] hidden link
The button Links are in the Homepage Slider, and are in 30% of the cases linked to the UK Content, instead of the Translated [WPML = NL | ES | De].
All pages are translated completely with Automatic Translation, and the problems seems to be "random | artifical"
Dear Support [Mr Long Nguyen] - perhaps Igemar [he knows this website well and has dealt with this before].
I made an Excel file of all lButton Links [from homepage to tourpage] for this Homepage Slider:
UK Default
WPML Translations in
= De [German]
= NL [Dutch]
= ES [Spanish]
Which provides a complete overview of which links of the slider are correctly translated, and which ones are NOT, [and direct to UK Default Language].
This list, made in Excel [green is ok, red is not! Okay. I can not upload the Excel file here.
Could you please provide me with an e-mail address, to which I can send this document [excel file]?
Regards,
Anton
file = called Homepage Slider Button Links
New threads created by Long Nguyen and linked to this one are listed below:
[NEW TICKET = PROBLEM regular LINKS | from "Product Tour Page" to "Tour Page]" = 16 Pages
Problem
Links from "Product Tour Pages" [regular link, called "more information" = 16 pages, to the "Tour Pages"
Two examples of these kind of pages [are all in SHOP] hidden link
2 of the 16 product pages in the UK language: hidden link hidden link
70% of the Links are not directed to the translated Pages but instead to the UK Default UK Content.
All pages are "translated completely with Automatic Translation," and the problems seem "random | artificial." I also updated the WPML Setting "Translate All Link Targets."
I made an Excel file of all these. I can not attach this Document [Excel file]. Links working are not marked | Links not working WPML Translated Link in NL | DE | ES "are red marked."
"Could you please provide me with an e-mail address"!, to which I can send this document [Excel file]?
Regards,
Ton TT
FILE = linked product to tour = "more information" links on Product Pages
[NEW SPLIT TICKET = WEIRD TRANSLATION = NO LOGIC = PROBLEM TRANSLATION PAGE = “ORGANIC FARMING”] hidden link
see the pages: hidden link [Dutch] hidden link [German] hidden link [Spanish]
Short background: I translated.
= alle pages and tours with automatic translation
= This page is 1 of the five volunteer pages in the 2nd menu [4 of 5 are translated correctly text-wise]!
This page is an exception; I even tried it twice [which is a waste of credits], and I also tried afterward with THE ATE. You can see the WPML Translation Live results on the website. The translated content is “bizarre”. It shows five pictures of the shop, which makes no Logic. None of the Default UK content is translated; it looks “weird.”
After the automatic translation of this page, I also reported this in the ATE Comment form and delivered these results without any s6. I can not find any reason or logic behind this.
Regards,
TON TT
New threads created by Long Nguyen and linked to this one are listed below:
[SPLIT TICKET = TOURPAGE SLIDERS] = 19 Pages in Total with this same Slider [UK Default URL].
I Translated all These Pages complete with Translate Automatically. These sliders appear on 19 pages = UK Default URL. [and are all the Same Template]. I also update in WPML all the “Translate Link Targets.”
In 50% or more cases, the [WPML Translation Pages in NL | DE | ES [Dutch | German | Spanish] link to the UK default Tour Page / Logdge Page / Contact Page instead of the WPML Translated Pages.
The URL list would be too long. It is one solution for all, as ALL these Sliders are the same.
First menu Tours
[Slider bottom Page = More Slides per Slider]
hidden link hidden link hidden link hidden link hidden link
hidden link hidden link hidden link
hidden link hidden link
hidden link hidden link
hidden link hidden link
First menu Lodges
[Slider bottom Page = More Slides per Slider]
hidden link hidden link
2nd menu Education
[Slider bottom Page = More Slides per Slider]
hidden link hidden link hidden link
Last year, we had the same problem; Ingemar from Support fixed it [he had to migrate the site]. This is a large and significant problem, but I think it.
This was the most significant problem last year, [[[with another SPLIT TICKET to FOLLOW] = [regular] BUTTON LINKS do not work on 70% of all WPML Translated Pages]]].
[SPLIT TICKET = REGULAR DIVI = “MAJOR” BUTTON Link PROBLEM = SITE OVERALL PROBLEM] = ALMOST ALL PAGES [UK Default URL].
I used automatic translation for all pages and products. Like the last translation during Nov / Dec 2023, we had the same problems. Ingemar from Support then managed it [it is almost one year later] = It seemed a complicated situation, as he [Ingemar for Support] needed to Migrate the Site to investigate the Issue. If there are problems, he has dealt with this Issue before on this website.
I hope [as this concerns all the websites and all translations and over 70% of WPML Button], direct to the UK Default Page instead of the translated WPML pages in NL | De | ES [Dutch | German | Spanish].
Regards,
TON TT [please see the Overview and [sometimes a small important detail in BOLD]
First Menu = Button Links from Tours:
Main Tour Overview = to hidden link
Sub Tour Overview = to hidden link hidden link hidden link hidden link hidden link
Tour Page = to hidden link 1 hidden link 2 hidden link 3 hidden link 4 hidden link 5
hidden link 6 hidden link 7 hidden link 8
hidden link 9 hidden link 10
hidden link 11 hidden link 12
hidden link 13 hidden link 14
Product Pages = to [from tour to product page = each page 2 buttons – besides Slider Tourpage]
hidden link 1 hidden link 2 hidden link 3 hidden link 4 hidden link 5
hidden link 6 hidden link 7 hidden link 8
hidden link 9 hidden link 10
hidden link 11 hidden link 12
hidden link 13 hidden link 14
First Menu = Button Links from Lodges:
Lodges Overview = to
hidden link
Lodges Pages = to
hidden link 15 hidden link 16
Product Lodge Pages = to [from tour to lodge to product page = each page 2 buttons – besides Slider Tourpage]
hidden link 15 hidden link 16
2nd Menu = Button Links from Education
Education Overview = to
hidden link
Education Tours = to
hidden link 17 hidden link 18 hidden link 19
= to Contact Page [from tour to lodge to product page = each page 1 button – besides Slider Tourpage] hidden link
2nd Menu = Button Links from Volunteer Programs [note = all bove buttons should be the same | these could be slightly different = built later = new pages = same button]
hidden link
Volunteer Programs = to [4 different volunteer programs [a,b,c,d}
hidden link a hidden link b hidden link c hidden link d hidden link e
a,b,c,d = to Contact Page [from tour to lodge to product page = each page 1 buttons]
hidden link
HomePage [at bottom] – three icons [all the same] 50% of translated fine, another one not correct to UK default Language
hidden link
Wildlife and Eco tours = to hidden link
Eco Lodges = to hidden link
Nature Conservation = to hidden link
I see you have other issues with translating a page and URL on the homepage. I will split this ticket into a new one for your new issues.
You can create many tickets as you want but please help us keep the ticket clean and easy to understand the issue by focusing on one issue per ticket.
If you don't have questions about sending content to translation in bulk, please mark this ticket as Resolved.
I closed the ticket BULK translation. The other outstanding issues I sent yesterday, September 3rd and 4th, are serious problems and still need to be resolved:
= homepage slider button links
= tour page slider button links = 19 pages = same slider
= backlink from product to tour page
= regular divi button [all over website]
= [after you reviewed 'organic page'], if all is okay, I can also close that ticket; I will wait for your reply,' If all I did is okay, after instructions
= SEO part, I think [a completely separate issue, among other SLUGS [needs to stay open if there is a ticket or to be opened
We are new | split tickets, which is the biggest challenge we will face. If you would like to go back [Ingemar dealt with this last year in November | December.
One year later, as there are very standard modules I used, I hoped this was = solved with structural ATE [between DIVI and WPML].
It is like it is; I hope we can solve these issues.
