254 results found

1. Add ODP segments as visitor group criteria

   As an editor I would like to make up visitor groups based on customer data from ODP. Profile properties, segments etc.
   I am aware of a community add-on that accomplishes this. But I believe this is something that is so important it should come from the Optimizely.

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Research & Design  ·  0 comments  ·  Personalization  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. [Feature request] Display forms in 'For This Site' and 'For This Page' sections when creating an EpiServer Forms criteria under Audiences

   Dear Team,
   Currently, when setting up EpiServer Forms criteria in Audiences, we can only select forms listed under the 'For All Sites' section. However, our business also requires the use of forms from the 'For This Site' and 'For This Page' sections.
   It would be helpful if future releases could include this feature.
   Thanks!
   Best regards,
   Lisa

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Research & Design  ·  1 comment  ·  Forms  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Allow ancestor/children links in Content Areas in Content Graph

   I am looking to get the parent/children of a content item that is used within a Content Area to support a hierarchical relationship. Currently, it is not possible to use the _link property on Content Areas within Content Graph.

   In this query:

   query MyQuery {
     MyPage(where:{ContentLink:{Id:{eq: 1119}}}) {
       item {
         ContentLink {
           Id
         }
         _link(type: ANCESTORS) {
           MyParentPage {
             items {
               Url
             }
           }
         }
       }
     }
     MyBlock(where:{ContentLink:{Id: {eq:1127}}}) {
       items {
         Cards {
           ContentLink {
             Id
             Expanded {
               _link(type: ANCESTORS) {
                 MyParentPage {
                   items {
                     Url
                   }
                 }
               }
             }
           }
         }
       }
     }
   }
   

   In the first query, we get back the parent items as expected, but in the second query we do not get any data for the _link. We should get back the same data in both.

   I am looking to get the parent/children of a content item that is used within a Content Area to support a hierarchical relationship. Currently, it is not possible to use the _link property on Content Areas within Content Graph.

   In this query:

   query MyQuery {
     MyPage(where:{ContentLink:{Id:{eq: 1119}}}) {
       item {
         ContentLink {
           Id
         }
         _link(type: ANCESTORS) {
           MyParentPage {
             items {
               Url
             }
           }
         }
       }
     }
     MyBlock(where:{ContentLink:{Id: {eq:1127}}}) {
       items {
         Cards {
           ContentLink {
             Id
             Expanded {
               _link(type: ANCESTORS) {
                 MyParentPage {
                   items {
                     Url
                   }
                 }
               }
             }
           }
         }
       }
     }
   }
   

   In the first query,… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Graph  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Research & Design  ·  AdminCiara Bergin (Principal Product Manager, Optimizely) responded

   Thanks for sharing this idea. Our product and design teams are looking into it now. We’re exploring possible solutions and figuring out what implementation could involve. We’ll keep you posted here as things progress.

4. Redirect page after expiration

   It would be great if it is possible te set a redirection (just like in the no-found handler) when a page is expired and is replaced by another page in the website. This would make the process much more user-friendly.

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Security & Compliance  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Future Consideration  ·  AdminMatthew Slim (Product Manager, Optimizely) responded

   Thanks for raising this - just to let you know this is now in our backlog. While we can’t share an exact release date yet, this means it’s planned for consideration in the future. Thanks for helping us prioritize this work.

5. Ability to add custom CAA records in a managed clients zone in Optimizely Cloudflare account
   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Future Consideration  ·  0 comments  ·  DXP, Hosting & Infrastructure  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Language Manager Role wise access

   In the Languages gadget (Language Manager add-on), users have the option to duplicate content when creating a new language branch. During this process, the “Duplicate content” dialog presents checkboxes for:

   Add all children

   Add related content(s)

   These options are useful for administrators but pose a risk when used by editors who may not fully understand the implications. For example, an editor in our organization mistakenly duplicated a section with over 800 nodes, resulting in around 500 duplicated blocks. This caused significant manual cleanup and unnecessary content clutter.

   Feature Request:

   We would like the ability to restrict visibility or access to these options based on user roles, ideally allowing only administrators or users with a specific permission set to see or use these checkboxes.

   Benefits:

   Prevents accidental large-scale content duplication by non-admin users.

   Reduces cleanup effort and risk of content sprawl.

   Adds a layer of governance around language branch creation.

   In the Languages gadget (Language Manager add-on), users have the option to duplicate content when creating a new language branch. During this process, the “Duplicate content” dialog presents checkboxes for:

   Add all children

   Add related content(s)

   These options are useful for administrators but pose a risk when used by editors who may not fully understand the implications. For example, an editor in our organization mistakenly duplicated a section with over 800 nodes, resulting in around 500 duplicated blocks. This caused significant manual cleanup and unnecessary content clutter.

   Feature Request:

   We would like the ability to restrict visibility or access to… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering Feedback  ·  0 comments  ·  Translations  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Customize the "Workflow status" Section in CMS UI Dashboard (v12.18.0+)

   CMS UI version 12.18.0 introduced a new dashboard with a "Workflow status" section. This section can display thousands of pages in some environments, each with multiple elements. This can result in a bloated and less usable interface, potentially affecting performance and user experience.

   We would like to request the ability to:

   1. Clear or limit the number of items displayed in the "Workflow status" section

   2. Filter the displayed items based on specific criteria (e.g., content type, date, language, or user)

   3. Customize or replace the section with a custom implementation if needed

   Providing more control or configuration options for this section would improve usability and scalability for teams working with large volumes of content.

   Reference: https://world.optimizely.com/blogs/matthew-slim/dates/2023/3/new-dashboard-implemented-in-cms-ui-12-18-0/

   CMS UI version 12.18.0 introduced a new dashboard with a "Workflow status" section. This section can display thousands of pages in some environments, each with multiple elements. This can result in a bloated and less usable interface, potentially affecting performance and user experience.

   We would like to request the ability to:

   1. Clear or limit the number of items displayed in the "Workflow status" section

   2. Filter the displayed items based on specific criteria (e.g., content type, date, language, or user)

   3. Customize or replace the section with a custom implementation if needed

   Providing more control or configuration options for this section would… more

   •  

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering Feedback  ·  0 comments  ·  Reports  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Database timeout during site starting up after removing properties of block type

   I am a senior developer. We have been facing this issue where when we remove properties of block type the site fails to start and throws database timeout during ModelSyncInitialization. This happens even when a single property of block type is removed.
   We have an open ticket with support and have tried a few solutions but the only option that works is to increase the DatabaseQueryTimeout to an hour or so.

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering Feedback  ·  1 comment  ·  DXP, Hosting & Infrastructure  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Cannot create custom folder-type instances inside shared blocks from the CMS UI

   In Optimizely SaaS CMS there is no way to create an instance of a custom folder content type (a content type based on the folder / _folder base type) inside a shared block through the CMS UI. The New Folder action creates only the built-in system folder type and offers no picker to choose a custom folder type. Separately, the New Folder action is currently not working at all in this context. As a result, custom folder instances can only be created via the Content Management REST API or Opal.

   Steps to reproduce:

   1. Define a content type based on the folder (_folder) base type and push it to the CMS.
   2. Open a shared block and go to the Assets panel.
   3. Try to create a folder using New Folder.

   Expected: The UI lets you create a folder of the custom folder type (e.g. a type picker), and the New Folder action works.

   Actual: New Folder offers only the built-in system folder type — no way to select a custom folder type — and the New Folder option does not work in this context.

   Impact: Editors can't self-serve folder organisation when custom folder types are involved — every folder creation needs a developer or an API call, which doesn't scale for content teams.

   Request:

   1. Fix the non-functioning New Folder action in the shared-block Assets panel.
   2. Allow creating custom folder-type instances from the UI (a folder-type picker on New Folder), consistent with how other content types are selected.

   In Optimizely SaaS CMS there is no way to create an instance of a custom folder content type (a content type based on the folder / _folder base type) inside a shared block through the CMS UI. The New Folder action creates only the built-in system folder type and offers no picker to choose a custom folder type. Separately, the New Folder action is currently not working at all in this context. As a result, custom folder instances can only be created via the Content Management REST API or Opal.

   Steps to reproduce:

   1. Define a content type based on the… more
   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  Editing (Content)  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Computed fields in Contracts

    Role: Developer working with Optimizely CMS 13 and Optimizely Graph.

    Problem:
    I am implementing search across multiple content types (pages, media etc.) using Optimizely Graph.
    A common requirement is to expose consistent search fields across different content types, for example SearchTitle and SearchDescription, while allowing each content type to derive those values from its own properties and fallback logic.

    The current limitation is that computed fields cannot be exposed through Contracts. While computed fields can be defined on concrete content types and avoid storing redundant search data, they cannot be used to create a unified schema across multiple content types.

    For search scenarios, fields such as SearchTitle and SearchDescription are really search projections rather than editor-managed content. To expose these fields through a Contract today, they must be persisted in the content model, even though they are derived projections rather than actual content.

    Desired outcome:
    Ideally, it should be possible to create a unified search schema backed by computed fields, without having to persist derived values in the content model.
    This would allow developers to expose consistent search fields across pages, media and other content types while keeping the content model free from search-specific properties and publish-time population logic.

    Role: Developer working with Optimizely CMS 13 and Optimizely Graph.

    Problem:
    I am implementing search across multiple content types (pages, media etc.) using Optimizely Graph.
    A common requirement is to expose consistent search fields across different content types, for example SearchTitle and SearchDescription, while allowing each content type to derive those values from its own properties and fallback logic.

    The current limitation is that computed fields cannot be exposed through Contracts. While computed fields can be defined on concrete content types and avoid storing redundant search data, they cannot be used to create a unified schema across multiple content types.

    … more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Graph  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Add .NET Counter publication to App Insights on Startup

    There are a whole suite of .NET counters available to use to publish to App Insights. This is a low-lift modification that enables us to gain many insights, directly inside of App Insights Metrics, we can utilize to diagnose issues on customers.

    This enables us to do performance investigations that otherwise require manual intervention (such as downloading .ETL files and opening them in PerfView or capturing dump files and analyzing them).

    We can skip these manual steps and jump write to "close to root causes" by publishing this information. There is little cost and no significant performance degradation associated with publishing this information because Microsoft has designed these metrics to be high performance to collect.

    Having this information available to us enables us to build further features such as success metrics into dashboards for partners to gauge the success of their implementation by taking this information and other information we've build into the Dashboard and surfacing it up in a useful way to the user base.

    There are a whole suite of .NET counters available to use to publish to App Insights. This is a low-lift modification that enables us to gain many insights, directly inside of App Insights Metrics, we can utilize to diagnose issues on customers.

    This enables us to do performance investigations that otherwise require manual intervention (such as downloading .ETL files and opening them in PerfView or capturing dump files and analyzing them).

    We can skip these manual steps and jump write to "close to root causes" by publishing this information. There is little cost and no significant performance degradation associated with… more

    • 

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Future Consideration  ·  0 comments  ·  DXP, Hosting & Infrastructure  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. IP Address restriction in Cloudflare

    It would be great if we could configure an IP Address whitelist in Cloudflare so that we only allow a specific set of source IP Addresses to be allowed to access our DXP instances. This will allow us to block public access to non-production environments

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  DXP, Hosting & Infrastructure  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Media name

    Currently, media asset names are getting cut off or wrapped based on the media field length. As a result, authors have to hover over each asset to manually note the full name before proceeding.
    Could you please add a feature where the added media item's name along with the path can be viewed and copied directly from the CMS.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Gathering Feedback  ·  0 comments  ·  Media / Asset Management  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. rolling restart flag

    Please make i possible to be able to flag for a rolling restart (one instance at a time) when executing deployments -through DevOps / GitHub release pipelines.
    -Note:
    old feature request disappeared it seems:
    https://world.optimizely.com/forum/developer-forum/Developer-to-developer/Thread-Container/2023/5/is-it-possible-to-do-a-rolling-restart-from-an-api-call-powershell-cmdlet-or-something-similar/

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Gathering Feedback  ·  1 comment  ·  DXP, Hosting & Infrastructure  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Improve “Select All” behaviour for lazy loaded export

    We’ve received reports from our users regarding confusion when exporting form submissions.

    Currently, when users click the header “select all” checkbox, the label shows:
    “All 25 posts are selected.”

    Because only 25 submissions are initially loaded, the checkbox correctly selects only these items. However, users often interpret this label as indicating that all existing submissions (e.g., all 69) have been selected - even though the remaining items have not yet been loaded via lazy loading. This misunderstanding has led to incorrect or incomplete exports.

    To reduce user confusion and better reflect what is selected, we would like to request an update to the informational label. Specifically, we propose showing both the number of loaded items and the total number of submissions.

    Suggested format:
    “25 of 69 posts are currently loaded and selected.”

    This is a small UI update that would significantly improve the user experience and prevent misunderstandings around exporting submissions. We are aware of not selecting any checkboxes and clicking export causes all 69 (in this case) to be exported.

    We’ve received reports from our users regarding confusion when exporting form submissions.

    Currently, when users click the header “select all” checkbox, the label shows:
    “All 25 posts are selected.”

    Because only 25 submissions are initially loaded, the checkbox correctly selects only these items. However, users often interpret this label as indicating that all existing submissions (e.g., all 69) have been selected - even though the remaining items have not yet been loaded via lazy loading. This misunderstanding has led to incorrect or incomplete exports.

    To reduce user confusion and better reflect what is selected, we would like to request an… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Forms  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Site specific SearchProvider for Content Graph

    The package Optimizely.ContentGraph.Cms 4.1.0 introduced a SearchProvider that enables searching within the page tree.

    We would like this SearchProvider to respect the Query.SearchRoots property so that searches can be limited to the current page. This would be valuable for us, as we manage more than 60 sites with large amounts of content.

    With Find (Search & Navigation), we were able to override the SearchProvider and inject the search root ourselves, for example:

    public override IEnumerable<SearchResult> Search(Query query)
    {
    var startPageId = ContentReference.StartPage?.ID;
    var startPage = startPageId > 0 ? startPageId.ToString() : "1";
    query.SearchRoots = new[] { startPage };
    return base.Search(query);
    }

    We would appreciate similar flexibility or support in Content Graph so that search queries can be scoped.

    The package Optimizely.ContentGraph.Cms 4.1.0 introduced a SearchProvider that enables searching within the page tree.

    We would like this SearchProvider to respect the Query.SearchRoots property so that searches can be limited to the current page. This would be valuable for us, as we manage more than 60 sites with large amounts of content.

    With Find (Search & Navigation), we were able to override the SearchProvider and inject the search root ourselves, for example:

    public override IEnumerable<SearchResult> Search(Query query)
    {
    var startPageId = ContentReference.StartPage?.ID;
    var startPage = startPageId > 0 ? startPageId.ToString() : "1";
    query.SearchRoots = new[] { startPage };
    return base.Search(query);… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Gathering Feedback  ·  0 comments  ·  Graph  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Google Tag Gateway

    Support Google Tag Gateway with Cloudflare.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Gathering Feedback  ·  1 comment  ·  DXP, Hosting & Infrastructure  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Order of content fields in Content Graph _fulltext property

    When a text field is indexed by Content Graph in the _fulltext property, the values in the fields are appearing out of order from how they are configured in the CMS, where nested content is appearing before outer container content.

    For example, our page contains an accordion block. The accordion block has a content area which allows topics blocks. The topics blocks contain a rich text field.

    When querying graph the _fulltext property shows the values of the indexed content in this order:

    Topics block content
    Topics block name
    Accordion block name
    Container block name

    We would expect to see the content in reverse order where the outer block names appear above the inner content:

    Container block name
    Accordion Block name
    Topics block name
    Topics block content

    The customer is querying graph content to feed data into their own LLM, and the proper order of block or page contents is essential for the LLM since it affects how the model comprehends the context. For example, these blocks are being used as FAQ content, where the "question" is the name of the block and the "answer" is the content of the rich text field. Maintaining the order of fields here is critical to preserve the context of the content.

    When a text field is indexed by Content Graph in the _fulltext property, the values in the fields are appearing out of order from how they are configured in the CMS, where nested content is appearing before outer container content.

    For example, our page contains an accordion block. The accordion block has a content area which allows topics blocks. The topics blocks contain a rich text field.

    When querying graph the _fulltext property shows the values of the indexed content in this order:

    Topics block content
    Topics block name
    Accordion block name
    Container block name

    We would expect to see… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Graph  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminCiara Bergin (Principal Product Manager, Optimizely) responded

    We’re currently gathering additional feedback on this idea. If you have any more context, examples, or specific use cases, please share them - it really helps us understand how this would best support your workflow. Thanks for contributing to the conversation!

19. The email field in a created Form should be marked as type="email" for accessability

    When an editor creates a form with an email field, the field should be marked as type="email" to support the new accessability laws.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Gathering Feedback  ·  0 comments  ·  Forms  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Trademark & superscript text in content

    At the moment, there's no way to superscript trademark or registered symbols in the copy within the email. The only way to edit this is within an element.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Research & Design  ·  0 comments  ·  Editing (Content)  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating