Dave Beattie
Mar 16, 2021
  1118
(1 votes)

Episerver AJAX and standard MVC calls with Localization

This post is inspired by Stefan’s solution here.

Recently I was involved in a project replacing a custom translation solution on a client’s site with a more standard Episerver solution using Episerver Languages to translate content and DblocalizationProvider for static text.

One issue we ran into was with API calls and AJAX requests.  The site is an ecommerce site and there were several places where requests where directed through a standard mvc controller/action route, rather than going through Episerver content routing.  This proved problematic when attempting to return translated content such as error messages as we found the current culture was lost and the site was using the default culture. 

We settled on using an ActionFilter to retrieve the language code from the url.   Initially we had used Stefan’s implementation tailored to AJAX calls.  However, we ran into further issues as a payment gateway implementation was using an api method as it’s return url in order to process the payment status and either complete the order or return an error message.  This we created something that would retrieve the language code from any request.   

   

 public class StandardMvcRequestSetLanguageAttribute : ActionFilterAttribute
   {

        public override void OnActionExecuting(ActionExecutingContext filterContext)
        {
            if (filterContext?.RequestContext?.HttpContext.Request == null)
            {
                return;
            }

            HttpRequestBase httpRequest = filterContext.RequestContext.HttpContext.Request;

            if (filterContext.RequestContext.RouteData.Values["language"] != null)
            {
                var lang = filterContext.RequestContext.RouteData.Values["language"].ToString();

                Thread.CurrentThread.CurrentUICulture = CultureInfo.GetCultureInfo(lang);
            }         
        }
    }

  

We then discovered that Episerver wasn’t supported localized urls for non content paths (it’s perfectly fine for links to content that goes through Episerver’s routing.)  Therefore we also registered a basic path with the language code in.  Our ajax calls and the return urls for our payment gateway were now able to return translated error or success messages.

 

 

Mar 16, 2021

Comments

Johnny Mullaney
Johnny Mullaney Mar 22, 2021 05:08 PM

Nice post David!

Please login to comment.
Latest blogs
Preview multiple Visitor Groups directly while browsing your Optimizely site

Visitor groups are great - it's an easy way to add personalization towards market segments to your site. But it does come with it's own set of...

Allan Thraen | Sep 26, 2022 | Syndicated blog

The Report Center is finally back in Optimizely CMS 12

With Episerver.CMS.UI 12.12.0 the Report Center is finally re-introduced in the core product.

Tomas Hensrud Gulla | Sep 26, 2022 | Syndicated blog

Dynamic Route in ASP.NET Core When MapDynamicControllerRoute Does Not Work

Background Creating one of the add-on for Optimizely I had to deal with challenge to register dynamically route for the API controller. Dynamic rou...

valdis | Sep 25, 2022 | Syndicated blog

404 Error on Static Assets Within an Optimizely plugin

Background With the move to CMS 12 and .NET 5/6, developers are now able to build Plugins and Extensions using Razor Class Libraries (RCL).  These...

Mark Stott | Sep 23, 2022