How to fix incorrectly resolved multilingual links to the non-default culture in Sitefinity Ecommerce products

Jul 20, 2016
Knowledge

Title

URL Name

How-to-fix-incorrectly-resolved-multilingual-links-to-the-nondefault-culture-in-Sitefinity-Ecommerce-products

Article Number

000186976

Environment

Product: Sitefinity Version: 7.0, 7.1 OS: All supported OS versions Database: Microsoft SQL Server 2012 SP2

Question/Problem Description

Inserting links for cultures other than the default in Ecommerce products LongText Fields is causing them to be resolved incorrectly on the frontend.

Steps to Reproduce

Clarifying Information

Steps to reproduce:

Assume there are ProductEN and ProductDE products, both different translations of a General Product.
Add a link inside ProductEN's description (which is a Long text field of type RichText) to lead to LandingPageEn. All works as expected.
Add the link to the ProductDE translation to lead to LandingPageDe - a translation of the LandingPageEn page.

Result: ProductEN's link leads to the proper localhost/LandingPageEn page. ProductDE leads to a url of localhost/LandingPageDe which results in a 404 error.

Expected: ProductDE leads to localhost/de/LandingPageDe

Error Message

Defect Number

http://feedback.telerik.com/Project/153/Feedback/Details/135309-links-to-same-culture-not-working-for-cultures-other-than-the-default-when-placed

Enhancement Number

Cause

The issue is caused by a bug in Sitefinity.

Resolution

The bus is fixed with Sitefinity Internal Build 7.1.5202 - release notes: http://www.sitefinity.com/developer-network/forums/general-discussions-/internal-hotfix-builds#xtd_1FCk-UaMwcC3XrrPuw

Upgrade to that or later build will fix the problem and any newly added links in the Long text fields of Ecommerce products will be resolved correctly.

Fix your existing links:

1. Upgrade to Internal Build 7.1.5202 or later.

2. Open each product for edit in the Sitefintiy backend, and publish it. Do this for all translations of the product.

The links can be fixed using the API:

1. Backup the project and database.

2. List all available cultures in your Sitefinity project.

3. For each language load all products, load the value of their Long Text field.

4. Parse the links properly.

5. Save the proper value in the database.

Example:

var catalogManager = CatalogManager.GetManager();

var products = catalogManager.GetProducts();

//list all frontend cultures in your project in the followign manner

var langs = new string[] { "en", "de" };

foreach (var product in products)

{

foreach (var lang in langs)

{

using (new CultureRegion(lang))

{ //Get the value of the LongText field, and then parse the links properly

//Perform for all LongText fields

var currentLangVersion = product.GetString("Description");

var currentLangFixed = LinkParser.UnresolveLinks(gerVersion);

product.Description = currentLangFixed;

}

catalogManager.SaveChanges();

Workaround

Notes

Keyword Phrase

Last Modified Date

7/20/2016 2:12 PM

How to fix incorrectly resolved multilingual links to the non-default culture in Sitefinity Ecommerce products

Files(0)

Was this article helpful?

Was this article helpful?

How to fix incorrectly resolved multilingual links to the non-default culture in Sitefinity Ecommerce products

Information

Related Articles