After updating to Toolset Blocks 1.3.4, Toolset is no longer compatible with Weglot. When I auto-translate a page, the formatting doesn't look good. I've tried to reach out to Weglot, and they said it's something wrong with the code. I am using Toolset Blocks 1.3.2 in another environment, there's no issue, I am only experiencing the issue after the update.
Can you mark the next post private so I can share the links with you?
Hello and thank you for contacting the Toolset support.
I am not familiar with the Weglot plugin, so, when you say "When I auto-translate a page, the formatting doesn't look good" I am not sure to understand what you meant. Can you elaborate more? Maybe explain in steps.
1. I go to xxx
2. I do xxx
3. I expect to have xxx
4. Instead I get xxx
Can you give examples of broken format? Add screenshots if needed.
I confirm that the credentials are working, but I could not find where the translation is done, so I can run a small test.
After updating to Toolset Blocks 1.3.4, Toolset is no longer compatible with Weglot. When I auto-translate a page, the formatting doesn't look good. I've tried to reach out to Weglot, and they said it's something wrong with the code. I am using Toolset Blocks 1.3.2 in another environment, there's no issue, I am only experiencing the issue after the update.
languages that are OK after the translation: hidden link hidden link hidden link hidden link
language with the coding issue on the page: hidden link hidden link hidden link
Unable to translate at all, language selector disappears on the bottom right: hidden link hidden link
hidden link - uses Toolset Blocks 1.3.4 (This is the environment you have access to) hidden link - uses Toolset Blocks 1.3.2
Thank you for your feedback. I can see the issue on the listed pages.
If I understand well, all the issues on these languages appeared after Toolset Blocks update, right? Or did you also updated the pages or the translations? If yes, can you explain how the translation process is done?
I would also ask if it is possible to take a Duplicator copy of the site while using Toolset Blocks 1.3.2, so we can perform the update and have both sates available(before and after) for our debugging.
If I understand well, all the issues on these languages appeared after Toolset Blocks update, right?
Yes, the issue appeared after the toolset block update.
Or did you also updated the pages or the translations?
No other update was changed.
Can you set my next post as private so I can share the other environment with Toolset Blocks 1.3.2 with you?
My apologies for the late reply, but it took me a long time on my tests. The secondary languages' pages were taking between 600s and 1500 seconds to load, with an average of 800 to 900 seconds. Check this screenshot hidden link
So, I deactivated all other plugins and I switched to a default theme and I was still having these load times. Which rings a bell on how Weglot work, and I think that it reaches Weglot servers for data during every request.
The languages switcher were correctly generated, but they did not respond(open on click) until the page fully loads, sometimes before that, but after a long time.
I performed the update and tried these pages again. The default page was loaded in around 20 seconds, but the secondary languages' pages were taking the same times(800s to 1400s). All languages have generated the language switcher correctly except for Italian.
When I checked the generated HTML, I can see a "Weglot error API" in the place where the language switcher should be generated. This appears also on your updated site. Check this screenshot hidden link
<!--Weglot error API : -->
I think that we'll need Weglot help here to better understand the cause of the issue and fix it.
I assume that Weglot does save the translation on the site, and I wonder if there is a way to temporarily disable requests from the site to Weglot servers?
I wonder if the Weglot support can step in and see why there is this "Weglot API Error" generated on your updated site? Any information can help us narrow this down.
Please note, that I was only checking the issues on the languages switcher. After deactivating plugins, there is no way to check if the PDF viewer is correctly styled.
We can go that step, but I hoped for your help setting a clean install with a default theme and only Toolset plugins as I am not used to the Weglot translation setup. This will help us quickly check if it's a general issue in Flywheel's hosting or just happening with your website.
I am sure it would take you a couple of minutes and save all of us the time to wait for responses between us and the Weglot support team. Just set up 2 or 3 languages, translate 2 or 3 pages, and check if the update will break any of them.
In addition, I'll be on vacation for a week from the next hour, as I will be reaching my today's shift. So, I'd prefer to keep communication here to let my teammates that will help on this issue have all the details to keep working on this issue.
I have to do some more testing on my end, but if you can keep the ticket open for the time being.
I am experiencing the issue being "fixed" when I activate/deactivate all the plugins. Pretty much what you did to fix the other languages and that resolved the IT issue. I'll keep on testing.
I checked the erroneous pages again and they seem to work correctly, except for the Japanese translation. And I am wondering if you are still needing assistance with this?
