Portal Engine Questions on portal engine and web parts.
Version 4.x > Portal Engine > Use name path for URL path View modes: 
User avatar
Member
Member
endurit gmbh - 6/4/2009 3:16:35 AM
   
Use name path for URL path
Dear Kentico Support Team

I'm using two languages: de-DE and en-US.
I have checked the checkbox "Use name path for URL path" in the site settings.
I create a new page for the language de-DE. The field "Document URLs path" at Properties -> URLs is grayed out with the correct value and the checkbox "Use custom URL path" is unchecked.
Now I add for the created page the language en-US with another document name. The field "Document URLs path" is empty and the checkbox "Use custom URL path" is checked. Why the field "Document URLs path" hasn't a value which is grayed out and the checkbox "Use custom URL path" unchecked?
I want to have automaticly these values after creating a new page with two languages:
language de-DE
document name: Suche
document URL path: Suche.aspx
language en-US
document name: Search
document URL path: Search.aspx

How can I solve this problem?

I'm using Kentico Version: 4.0 Build: 4.0.3440 with portal engine and ASPX Pages.
I have the source code.

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 6/5/2009 2:03:37 AM
   
RE:Use name path for URL path
Hi,

Have you applied any of the hotfixes before? I see that your build number is higher than the latest hotfix - have you made any custom changes? If yes, what were they?

I have tried to reproduce your issue. I have set the setting according to your description and I have two languages A and B.

I have created new page for language A: "Document URL path:" is grayed out, "Use custom URL path" is false (unchecked).

I have now created language version B for this document: Document URL path:" is grayed out (with correct name in the B language), "Use custom URL path" is false (unchecked).

I got the same results when trying it backwards.

Could you please describe me the exact steps? Maybe I am missing something. Moreover, I have applied the latest hotfix for this CMS instance I have.
Thank you.

Best Regards,
Juraj Ondrus