Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: A Localized page with neutral child pages is possible but does not work correctly #6167

Open
2 tasks done
Timo-Breumelhof opened this issue Oct 21, 2024 · 1 comment

Comments

@Timo-Breumelhof
Copy link
Contributor

Timo-Breumelhof commented Oct 21, 2024

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

When you create a localized page with neutral sub pages, the menu stops rendering the correct child pages and the localization tab in the page settings in some cases behaves weirdly too.

Steps to reproduce?

FYI, the way we ran into this was on a site that had originally only one language where others were added later.
But here's a way to reproduce the issue:

  1. Create a new Portal
    image

  2. Add extra languages (I used Nl-nl and Fr-fr)

  3. Switch on Content Localization without translating existing pages.
    image

  4. Create a page "webshop"

  5. Go to Localization and make the page "Language Neutral"

  6. Create some child page webshop/payment

  7. Go to Localization and make this page also "Language Neutral"

  8. Add the missing language for the "webshop" page and make sure they are Translated and Published

  9. Create the page "webshop/ML" and make sure it's fully translated.

Current Behavior

When you visit the en-US page, you will see the subpages of the Webshop page in the menu.

image

When you switch to one of the other languages, you can visit the payment page, but it does not show up in the menu.

image

The payment page is also not visible in the Page Settings Tree

Expected Behavior

IMO it should be able to have a "language neutral" page as a child of a translated page.
Or if it's not supported DNN should warn you

Relevant log output

No response

Anything else?

I have seen very weird other issues, which seem related to this, but I have not been able to reproduce them on a clean site.
On the client site we have about 10 child page of webshop and one of those has again 5 child pages.
(mix of neutral en translated pages)
Also the default language is nl-nl for that site and not en-us (not sure that's even relevant)
I'll list them for reference:

  1. The nl-nl "webshop" localization tab sometimes only shows the "nl-nl" language and sometimes it shows all languages
  2. Sometimes on the nl-nl site webshop page links to the French webshop page.
  3. Sometimes the logo on the FR site links to the Nl-nl home page

I tried reproducing these but it seems random..
FYI, I checked the DB for localization issues and these all seem fine.

One other thing I noticed:
When you try to get out of this issue by making all pages ML you run into a related issue.

Reproduce:

  1. Create a neutral page "Webshop"
  2. Create some child-pages that are "translated".
  3. Now make the "Webshop" page translatable too.
    Result: I noticed that the child pages are now still children of the "Webshop" page in the main language and not the translated "webshop" pages.

This is the situation I ended up with:

image

I think the only way to get out of this is by DB manipulation as they don't show up in the menu any more.

Affected Versions

9.13.4

What browsers are you seeing the problem on?

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@Timo-Breumelhof
Copy link
Contributor Author

As an FYI, I also found why we had links to incorrect pages in the menu (DE pages in the NL menu).
It's a combination of settings, very weird, but I managed to reproduce it and will log that one too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant