Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

All other Modules /

Discuss all other Modules here.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

Same URLSegment for a similar page in another language?


Go to End


4 Posts   1786 Views

Avatar
c.scherer

Community Member, 1 Post

13 December 2010 at 10:18pm

Edited: 13/12/2010 10:18pm

hello SilverStripe-community,

i'm actually working to get silverstripe running in different languages. the structure should look like this:
eg. -> /enu/shop/details/10 (english version)
and -> /deu/shop/details/10 (german version)

the first URLSegment ist for the language and the region.
i already found a solution getting these language-folders working. but now the problem is - silverstripe prevents duplicate URLSegments in the SiteTree-table.

now my question: where i can find the point where SS appends the "-de-DE" / "-2" at the URLSegment?

i'm using the actual silverstripe 2.4.3.

thanking you in anticipation!

kind regards,
christian

Avatar
suntrop

Community Member, 141 Posts

10 August 2012 at 8:30am

Hi

Did you find a solution for that? I am currently facing the same problem in 2.4.7

Avatar
jand

Community Member, 30 Posts

14 August 2012 at 8:28pm

Hi, we had the same issue. As a workaround we just used one page in the pagetree root and put all other pages as childs. This "root page" has a custom pagetype "language". It has no content but the /en/ URL segment. Not the most elegant way but it works.

Avatar
suntrop

Community Member, 141 Posts

15 August 2012 at 5:10am

Ok, so you put in the "en" from a custom field int your language pagetype, right? But that doesn't solves the problem with same URLSegments? Am I wrong?