[Closed] Conflict with Avada Options: portfolio slug - header content - logo

I am trying to: translate Avada Options (AO) in a consistent way (String translation or Avada Options panel in each language) without getting errors on the front end for>

1) portfolio post type slug (main CAT "pellicules" / ESP "peliculas" / ENG "films")
2) the top header content ( CAT "Del 8 al 18 de...")
3) the main logo (CAT "FIRE!! L´Amor tot...")

///////////////////
1) The slug is set in Avada options/Portfolio/General Portfolio.

At first I set the translations in the AO for each language. Conflicts*.
Last year a supporter told me that the right way to translate it was through String translation. I did it and it sometimes it works well for some time. But then..

---> If you change any setting in the AO, or just after translating pages and sometimes for unknown reasons (but clearly after using WPML in one or other way):

1.1) The URLs of the portfolios in the movies grid** (hidden link), link to an image instead of the corresponding portfolio page, or wrongly point to their ENG version. It sometimes happen on the ESP/ENG versions too.

**("The Grid" plugin is installed now but I got the same errors with Avada´s portfolio element, so it´s not the plugin)

1.2) 2) and 3) get reset.

__________
2) This content is set in AO/Header content/Phone Number.
__________

CAT "Del 8 al 18 de juny 2023 • A l´Institut Francès i a Filmin"
ESP "Del 8 al 18 de junio 2023 • En el Instituto Francés y en Filmin"
ENG "June 8 - 18 2023 • Presential and at FILMIN"

They are translated in WPML strings. They do not display on the frontend.
So I had to enter the translations in AO for each language. This creates conflicts with 1).

Right now you´ll see it´s an "hybrid" as in AO the ESP version is in CAT but if I change it to ESP it creates conflict with 1). The ENG translation is set in AO in ENG and works fine on the front end.

__________
3) This content is set in AO/Logo
__________

To temporarily fix 1) I saved the AO having the "All languages" switcher selected (so far it´s the only way to fix it) with the main-CAT version of it. The file has been translated through Media Translation. Sometimes it displays correctly, but after doing the "fix", it doesn´t any more.

*FYI> this website is not new and I´ve been experiencing this for the last 2 years.
Every time my customer reported the error (quite often), I tried to fix it following these steps (sometimes they worked):
> Resave the portfolio slug in the Avada options (using the same term) and then erasing and retranslating it´s String translation
> this leads to the reset of the Top header and main logo translations, which even though they are translated through String translation they do not display on the frontend unless I enter it´s translations in the AO X@
> resaving the permalinks
> clearing WPML cache...
> running WPML troubleshooter

Link to a page where the issue can be seen: hidden link (Right now is "temporarily fixed" as explained above because it´s a live site with a big campaign running.) but it´s quite easy to recreate the problem, just by changin the logo and/or phrase in the AO translations.

I expected to: be able to translate AO in a simple way (either through String/media translation or for each language in the AO) and see the reight translations on the front end 🙂

Instead, I got: unstable display of translations on the Front end, portfolio links failing randomly and inconsistant way of translating