Vulnerability in EPiServer.Forms

Try our conversational search powered by Generative AI!

Giang Nguyen
Feb 23, 2021
  2437
(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

Pros:

  • Easy ans effortless 

Cons:

  • 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.

    [InitializableModule]
    [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)
                {
                    continue;
                }

                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;
                    _propertyDefinitionRepository.Service.Save(clone);
                }
            }
        }
    }

Pros:

  • 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

Cons:

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

Comments

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
Google Read Aloud Reload Problems

Inclusive web experiences greatly benefit from accessibility features such as Google Read Aloud. This tool, which converts text into speech, enable...

Luc Gosso (MVP) | Dec 4, 2023 | Syndicated blog

Google Read Aloud Reload Problems

Inclusive web experiences greatly benefit from accessibility features such as Google Read Aloud. This tool, which converts text into speech, enable...

Luc Gosso (MVP) | Dec 4, 2023 | Syndicated blog

Import Blobs and Databases to Integration Environments

In this blog, we are going to explore some new extensions to the Deployment API in DXP Cloud Services, specifically the ability to import databases...

Elias Lundmark | Dec 4, 2023

Join the Work Smarter Webinar: Working with the Power of Configured Commerce (B2B) Customer Segmentation December 7th

Join this webinar and learn about customer segmentation – how to best utilize it, how to use personalization to differentiate segmentation and how...

Karen McDougall | Dec 1, 2023

Getting Started with Optimizely SaaS Core and Next.js Integration: Creating Content Pages

The blog post discusses the creation of additional page types with Next.js and Optimizely SaaS Core. It provides a step-by-step guide on how to...

Francisco Quintanilla | Dec 1, 2023 | Syndicated blog

Stop Managing Humans in Your CMS

Too many times, a content management system becomes a people management system. Meaning, an organization uses the CMS to manage all the information...

Deane Barker | Nov 30, 2023