1-888-365-2779
+1-888-365-2779
Try Now
More in this section

Forums / Developing with Sitefinity / Problem in adding hyperlinks in multi language site

Problem in adding hyperlinks in multi language site

3 posts, 1 answered
  1. mohudoom
    mohudoom avatar
    6 posts
    Registered:
    11 Aug 2008
    07 Oct 2009
    Link to this post
    Hi,

    We have a sitefinity site with multiple languages. When adding hyper links in editor its added like <a href="/Page.aspx">Page</a> . but when clicking on hyperlink, is always taking to default language when mulitple languages is used.

    But when we edited the html code and changed to <a href="./en/Page.aspx">Page</a> or <a href="/ar/Page.aspx">Page</a> its loading correct language pages.

    Is there any way we can customize this to add the language specfier when adding links to page?

    Thanks
    Faluludeen
  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    16 Jun 2017
    07 Oct 2009
    Link to this post
    Hi mohudoom,

    Most probably you are using one of the Sitefinity versions before 3.6. From 3.6 we are using dynamic links. However, by default we resolve the relative path and the culture is skipped. This means that the url is opened depending on your current culture. If your current culture is "en" the format of a page your will be "domain.com/en/page.aspx". When your current culture is different ( say "bg") the url format will be "domain.com/bg/page.aspx".

    In your case you could upgrade your project or try enabling module localization. When module localization is enabled the path prefix should depend on the language version of your content item.

    Kind regards,
    Ivan Dimitrov
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
    Answered
  3. mohudoom
    mohudoom avatar
    6 posts
    Registered:
    11 Aug 2008
    14 Oct 2009
    Link to this post
    Thanks. upgraded to sitefinity 3.7 and that solves the problem
Register for webinar
3 posts, 1 answered