[Closed] Several issues translating our website

Hi Bruno

Let's take the first link as an example. It's pointing to hidden link in the english original.

I then use the WPML translation editor to translate that page, which works fine for the titles and button texts. But as far as I know, the translation editor should match the english links from the original page to the german link in the german translation and the french link in the french version. This also works for all the links to pages, but not for the links that point to the "institution" post type (hidden link). All those links are mapped to /fr/ instead of /de/. I want to find out, why this is. Can you shed some light on why WPML is doing it that way? To further investigate, I added an additional button (blue) that points to another post type. There, the german version correctly points to the /de/ path and the french translation to the /fr/ path.

I thus assume the problem is related to the institution post type. Maybe it's also connected to the other problem I mentioned at the beginning, that we get a ciricital error on some of those posts (e. g. hidden link or hidden link). I didn't experience this issue with any other post types.

Thanks for your support.

I'll work on the new environmen as soon as possible. Please keep the ticket open.

Hi Bruno

I was able to replicate the exact same issue.

Test page that points to three example institutions: hidden link

German translation: hidden link --> The links point to French for those posts that were translated and to English for the one that I deliberately didn't translate.

Below on the test page is another button for a different post type, there it works as expected.

I'm looking forward to your feedback.

Best,
Marcial

Hi Bruno

Okay, thanks for letting me know.

There is a second issue with Avada the team should look into: when resetting the Avada cache in the original language, it works, but in other languages we get a 403 error.

hidden link > Performance > at the very bottom

This error is reproducable across all our projects with Avada and WPML. But it worked in the past - I discovered this behaviour a few weeks back for the first time.

Thank you!

Hi Bruno

You offered to do that for me. Quote: "We can cover only one issue per ticket, so let's focus on 1st one and I will split it into new tickets later."

Could you do that? That way you could provide access to the test website you created directly to your team and be my contact person for the ticket.

Thanks

Hi Bruno

I can confirm that this seems to fix the issue with the incorrect links in the translations. I discovered a second CPT with the same issue and by setting that cpts slug too I fixed it for those links as well.

Can we therefore state that we have to always set a slug manually for each language even if the slug is the same in all languages? Is that correct?

1) should be done, and fortunately it also seemed to have fixed 2) as well, but let me double check that on the live site too.

I'll then reevaluate 3) and let you know if that still is an issue.

Thanks a lot for your help so far, it's much appreciated!