You can get weird redirect issues when there are issues in the database (I have not yet found what caused these).
Try this:

<code>SELECT<br />     <br />     Tabs.TabID,<br />     Tabs.PortalID,<br />     Tabs.TabName,<br />     Tabs.ParentId,<br />     Tabs.TabPath,<br />     Tabs.IsDeleted,<br />     Tabs.CultureCode as TabCultureCode,<br />     ParentTabs.TabName as ParentTabName,<br />     ParentTabs.CultureCode AS ParentCultureCode,<br />     Tabs.Level as TabLevel,<br />     ParentTabs.Level AS ParentLevel<br /> FROM         Tabs INNER JOIN<br />                       Tabs AS ParentTabs ON Tabs.ParentId = ParentTabs.TabID<br /> WHERE NOT Tabs.ParentId IS NULL AND not (Tabs.CultureCode = ParentTabs.CultureCode) and tabs.PortalID = x</code>

Hello,

That query gives no output record. Thanks for looking into it.

Please lte me know if you see some other cause.

Regards,

Alok

Posted By Alok Agarwal Official on 3/21/2023 8:06 PM

That query gives no output record. Thanks for looking into it.

Did you change the PortalID (x) in the script to the actual PortalID (normally 0)?

Happy DNNing!
Michael

Adding our requirements to make it more clear:

1. We already have our web site localized in three langauges (en-us, es-es, fr-fr). 
2. We want to enable our website for two more langauges (i.e. de-de, pt-br). Content is to be added subsequently by translators in some time. Mean while we want if any users in these language should redirect to fallback language - i.e. en-us.
3.Once the content is localized, we want site in that language to be active, so that our clients can access the pages.

To our understanding we have done following configurations/settings for this:-

1. Enabled the site, not activated for the two additional languages in site settings. I think this should allow translators to create the content.
2. Set fallback language as en-us for the two languages.
3. Since the site is not activated, additional languages should not pop for client in language tool bar.
4. If the clients of additional languages (i.e.  default browser culture is set to new languages), it should redirect to fallback language.
5. We plan to activate the language once the content is localized by translators.

Issues here are:-
1. If the clients of additional languages (i.e.  default browser culture is set to new languages)--> When the user logs in(login page in neutralize, i.e. no language is shown) they get to see pages in french language.
2. At times also saw language code de-de(for deutch users) is coming in url after login, menu bar goes off(which is understandable as underlying pages are not yet translated). But question here is why it is coming in url if we haven't activated it.  
3. What is concept of fallback language, how can we use it?
4. Is there any more setting/configuration which we need to look into.

yes that was obvious for us.

Posted By Alok Agarwal Official on 3/22/2023 1:30 PM

Adding our requirements to make it more clear:

Issues here are:-

1. If the clients of additional languages (i.e.  default browser culture is set to new languages)--> When the user logs in(login page in neutralize, i.e. no language is shown) they get to see pages in french language.
2. At times also saw language code de-de(for deutch users) is coming in url after login, menu bar goes off(which is understandable as underlying pages are not yet translated). But question here is why it is coming in url if we haven't activated it.  
3. What is concept of fallback language, how can we use it?
4. Is there any more setting/configuration which we need to look into.

1. Did you check if these French pages (could that be the home page?) are not marked as "Translated" under Pages > Page > Localization?
Also, Did you try unchecking "Enable Browser Language Detection" as a test?

3. That's the language DNN uses if there is no translation for a static text. I general I leave that at EN-US
4. Yes, make sure you have a "neutral" and one Portalalias per language defined under Site Settings > Site Behavior > Site Alias and set that to primary (only one per language).

Yes I have chaked all of these settings, they are as expected. Will try more for "Enable Browser Language Detection" as a test. Also wanted to know what settings are expected to be for URL  mapping, if that can help:

URL MAPPING

Site Alias Mapping Mode

• Canonical
• Redirect
• None

Auto Add Site Alias

Regards,

Alok

Unchecking "Enable Browser Language Detection" didnt helped. Any other solution we can try?

What I would do is try the same (just the language pasrt with only a few pages) on a clean install of DNN also to make sure it's not a bug in DNN.
(We have also run ML installations, but most of them are only public facing and not with members logging in)
Also that would give you something to compare with if it does work correctly on the new install.
Becasue I guess it's some kind of configuration issue.