Ryan Lewis

Aha - it looks like you have installed it as an Umbraco package - did you also install it this way @trevorloader ? I usually use Nuget to install this...

[This guide](https://our.umbraco.org/documentation/getting-started/setup/install/install-umbraco-with-nuget) is considered the most up to date. I would always recommend managing projects this way - it allows you to update Umbraco easily, and many other extensions now...

Had a little look into this at the minute. I'm not entirely sure this is currently possible as the current culture doesn't seem to be available at publish time to...

I've written a post on our.umbraco.org regarding these issues. https://our.umbraco.org/forum/developers/api-questions/65242-UrlSegmentProviders-and-the-current-culture-(SEO-Metadata-playing-nice-with-Vorto) At the moment the core doesn't make it possible for the UrlSegmentProvider to grab the current culture for the page...

I saw that and that's what I've been looking into. What Matt suggested is exactly what SEO Metadata is doing currently. Unfortunately that method cannot get the current culture so...

The request pipeline does. The problem is that you are configuring the URL name, which is a publishing/backoffice thing and not a content thing.

`GetVortoValue` is an extension method for `IPublishedContent`, where content in this case is `IContentBase`. The `GetVortoValue()` method also uses `Thread.CurrentThread.CurrentUICulture`. `GetVortoValue` is intended to be used at render time.

Looks like this issue will have to wait until v8 of the Core until it is resolved. http://issues.umbraco.org/issue/U4-7130

It's something I definitely see being useful. Unfortunately I don't have much experience with the dictionary or multilingual sites and it isn't a feature our clients will benefit, but will...

Think this will wait until 7.3 at the earliest, due to some changes in the way localisation is done in that version. Check the [roadmap](https://our.umbraco.org/contribute/roadmap)