Giang Nguyen
Feb 23, 2021
(1 votes)

Localize Forms post-submission actors

The "Send email after submission" actor for Episerver Forms are not marked as LanguageSpecific. That's a real struggle for editors when they want to customize the email response for each language version.
I'm not sure about the background why this is not translateable by default. 

However, there are a few workarounds for this trouble.

Use the "Edit propery" function in CMS Admin


  • Easy ans effortless 


  • Not safe
  • The setting might revert back to default after IIS recycle, nuget update or code deployment
  • The translated data will be lost (permanently!) if the property reverts back to default

Programmatically update the property attribute

We can create an initialization module that executes after Forms finishes its init tasks.

    [ModuleDependency(typeof(EPiServer.Forms.EditView.InitializationModule))] // Should initialize AFTER Epi Forms
    public class FormsLanguageSpecific : IInitializableModule
        Injected<IContentTypeRepository> _contentTypeRepository;
        Injected<IPropertyDefinitionRepository> _propertyDefinitionRepository;

        public void Initialize(InitializationEngine context)
            var containerTypeList = typeof(IFormContainerBlock).GetDerivedTypes();
            foreach (var containerType in containerTypeList)
                var formContainerContentType = _contentTypeRepository.Service.Load(containerType);
                if (formContainerContentType == null)

                var actors = formContainerContentType.PropertyDefinitions
                    .Where(p => p.Type!=null && p.Type.TypeName != null 
                        && p.Type.TypeName.Equals("EPiServer.Forms.EditView.SpecializedProperties.PropertyEmailTemplateActorList"));
                foreach (var actor in actors) // Iterates through all actors (incl. custom actors)
                    var clone = actor.CreateWritableClone();
                    clone.LanguageSpecific = true;


  • Don't need to worry about many msitake when using the Admin UI
  • It permanently changes the property (almost)
  • Personally, I haven't seen any issue after updating/deploying


  • The site will fail to start in case of internal Forms code refactors
Feb 23, 2021


Kane Made It
Kane Made It Feb 23, 2021 05:01 AM

Hi Giang, if the property value is changed after deployment/IIS reset, should we report it to internal team who curently in charge of Form? Lately I've encountered issue with edit mode preview with fixed DOM and I reminded the team also.

Giang Nguyen
Giang Nguyen Feb 23, 2021 06:28 AM

Hi Kane, the changes of properties I mentioned is after upgrading nuget packages or change the assembly version. Any of such change would trigger a data type synchronization. Looks like a by-design behavior when property attributes revert back to default.

Back the this post, I have no knowledge about the background of why post submission actors are not language specific. So, this would help in multilingual context :)

Please login to comment.
Latest blogs
The 1001st Piece in your 1000 Piece Puzzle: .NET Default Interface Functions

I was recently working with a client who wanted a reasonably large subsystem added to Optimizely that would add automated management to their...

Greg J | Nov 28, 2022 | Syndicated blog

Video Demonstration, creating a CMS12 Alloy Sample Site

Hey All Below you will find a quick video demonstration on how to install a local version of Alloy Sample based on CMS12 / .Net 6. As you will see ...

Minesh Shah (Netcel) | Nov 28, 2022

How to create an admin user I Optimizely CMS – with Episerver CLI

In this blog post I’ll show how to create an admin user for Optimizely CMS in a new environment where you don’t have access to the admin interface.

Ove Lartelius | Nov 28, 2022 | Syndicated blog

Optimizely shortcuts in CMS 12 will get a trailing slash appended!

Not all URLs will work when the trailing slash is added, and that could cause problems. Hopefully it will be fixed soon.

Tomas Hensrud Gulla | Nov 26, 2022 | Syndicated blog