I have a site with multiple languages set up with the default being en-US. For the default language pages I'm using advanced URLs and setting the URL for a lot of the pages in the Page URL field in the Page Settings. So instead of site.com/parent-page-name/child-page-name, I'm setting it to site.com/page-url, and the navigation works perfectly. I localised the site to another language and have the portal alias site.com/de set to that language. For the new localised pages I've updated the Page Name and also the Page URL for that language. But now when I go to site.com/de the menu uses the urls: site.com/de/parent-page/child-page. When I go to site.com/de/page-url the page loads fine. How can I force the navigation to use the Page Url field for the navigation in the localised pages of the site?

I'm using DDRMenu, but I've also tried different menu modules but with the same results.

I'm using DNN 7.1.2 Community.

I’m having the same issue. Since I have already created a text with this issue, I’ll leave it here. Maybe it becomes more clear.

 

In a localized content scenario, I want to have pages in PT and in ES to have different custom URLs for each locale.

The “Page URL” field, on page details tab when we go to the “Page Settings” for a page, does not work for other pages than the main locale. The URL specified is recognized and does not provoke a redirection. But the problem is that the custom URL is not used in the menu links or when inserting a hyperlink in HTML. It always uses the URL derived from the page name.

 

This is now invalidating me to use DNN as a platform for developing multi-locale sites with SEO in mind!!!!!

 

I’ve tested this on DNN 07.02.01 (367) and DNN 07.02.00 (607).

 

Any solution or workaround? Or I’m doing something wrong?

 

Regards

ztp

that's not qyite correct - the field you're seeing is the version it's first reported in (also the issue is still open) - when an issue is fixed it will be marked as resolved/closed and the fix version field will be filled in to let people know which version it was fixed in. As for commenting, jira requires a user so click "login" in the top right and then create user -after which you can raise issues, add comments, track progress etc. Sacha never returned to confirm the issue was fixed hence we've left it open - if you can add a comment with the steps necessary to reproduce then it's more likely we'll schedule it to get fixed (as at the minute we don't know if a fix is required or not)

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US