Big problem with multilingual sites on Helix Ultimate 2.0.7

yes the forum sucks , because of so many issues and bugs for each new release joomshaper team prefer not to share fix and solutions with all customers. if you have a problem just use akeeba backup its better for you.

Please @Toufiq, it is very important that they solve the problem, as @Pavel says it is a known problem since version 2.0.5, which they provisionally solved and now it comes up again. See my post here
https://www.joomshaper.com/forum/question/11955

"Please release a quick update for multilanguage. It is a problem that we already suffered in version 2.0.5 and it was solved in 2.0.6, therefore it is a known problem. Don't make us wait two months like last time. It is a problem that seriously affects all of us who use multilanguage, which are many. Thanks"

Here the original problem in version 2.0.5 and the solution they offered us, there are corresponding screenshots.
https://www.joomshaper.com/forum/question/6957#qa-answer-42505

As @Pavel comments, just by creating a multilingual site with its main menus, you will notice that the menus corresponding to the language do not appear.
It is a serious problem, it does not allow us to work with multilingual sites

Hello @Toufiq!

After updating to version 2.0.7, the problem recurred here.

Hi @Paul

" About Menu problems in multilingual site, go to menu items and select template for each language, then it should work. In case of... share access, I will check."

Hi, @Paul Frankowski.

Obviously that's how it works, but it's a real botch. It is not the normal operation of Helix Ultimate 2. Please solve the problem, you already know the cause, colleague Stéphane Falang Team explains it here

https://www.joomshaper.com/forum/question/6957#qa-answer-42505

Hi, I would appreciate knowing if the problem was communicated to the developers and if it will be corrected in the next version. Thanks

Almost 2 months have passed, Helix Ultimate 2.0.8 update has been released, but this fatal bug is still not fixed. This is epic fail!

Joomshaper team is coordinated? Your will is to ignore the problem? Listen to the users and fix the multilanguage problem in Helix Ultimate

Problem commented on your twitter, it may be more effective, so they stop ignoring us

Dear Paul, this is the alternative solution that you now propose, I have been subscribed to all the brand's products for years, the HU has not worked like that from the beginning, it has always worked without assigning the templates to the menu items.

https://www.joomshaper.com/forum/question/6957

You have recognized the problem in version 2.0.5, you have released an update to solve it, in version 2.0.6 the problem is solved. In version 2.0.7 and 2.0.8 it shows up again. The least they can do is recognize it and not treat us as ignorant.

Its developer has known about it for a long time, just like all of you, they have even changed the Helix Ultimate 2 multilanguage documentation. I can only think of one reason why the problem is not fixed, which is a possible incompatibility with the Page Builder. or any of its extensions. I don't see any interest in fixing it.

Finally it seems this topic has activity. Can't you share the files to test them? I can not enter the admin to check the solution to the multilingual problem. I would also ask you to publish this post to the multiple threads of the forum where this topic is discussed, to see if the affected users can validate the solution

I tried to switch langugages in the demo page you posted but still there is only the english menu, no matter what language I choose. so in your example there is nothing to test

@webfeuerflo you are right, but I want to think that the menus are different for each language but the items have not been translated. Any other option would seem like a bad joke to me. That's why I ask for admin access or test the update. I understand that after so long, we are all disappointed with the Joomshapper team and don't trust their promises too much.

I don't understand, what takes them so long. Stephane from falang already proposed a fix that works. I manually edited a file of the helixultimate plugin and the translation of menus works. I know that I will lose this fix as soon as I update as long as joomshaper does not implement it

and if the menu items have not been translated, the demo does not make any sense at all, because you can not tell if it works or not

@webfeuerflo, I have entered as admin in http://helix-framework.org/helixnonhelix/ and I have activated the multilingual option, I have translated the ES menu and translated the items, it seems to be displayed well

@webfeuerflo after seven months with this problem, I can only think of three options as to why it hasn't been solved before: 1. Lack of team coordination (ruled out), 2. solving this problem conflicts with some important extension or is incompatible with some extension current or future (probable) 3. They prioritize the quantity of templates and extensions but not the quality (likely)

Hello, Toufuq.

I checked on 3 sites, everything is working great now. Thank you.

Hello, I have done a quick test, it seems that the update solves the problem of the multilanguage menus. Attention: when activating the CSS compression, the Font Awesome icons of social networks disappear

It seems that on your live server the Font Awesome problem does not occur, I have only been able to test it on localhost

Hi guys,

This issue seems to be back. When using the latest version of FaLang and Pagebuilder again we have no translated menu items and URL's.

Can you please get this sorted ASAP and keep us posted on the progress?

Thanks!

The issue is there in the free version as well, so no need for the pro. And I'm sure Stephane (the creator) will provide you with a free pro version should you need it. He's usually very quick to respond and helpful.

Just an update from my side: after some more digging it turned out it had something to do with the age-old plugin order. When you just visit the 'Falang > Control panel' page in the backend, the order is restored to its correct position and it all works fine. At least when using the latest versions.