183 results found

1. Preview unpublished content delivered by Content Delivery API

   In the documentation it says that it is possible to enable previews of unpublished content delivered by Content Delivery API https://docs.developers.optimizely.com/content-management-system/v1.5.0-content-delivery-api/docs/customizing-content-delivery-api-for-edit-view. However the example that is provided wont work since HttpContextContextModeResolver that it uses checks for values in the current request that indicates that the request is made to the cms edit mode.
   This will never be true when you are using Content Delivery API to fetch the content since the request is made to /api/episerver/v3.0/content/... and not /episerver/cms/...
   In my opinion, Optimizely should have a built in way of previewing unpublished content delivered by Content Delivery API or at least a solution that we as developers can implement in our projects.

   In the documentation it says that it is possible to enable previews of unpublished content delivered by Content Delivery API https://docs.developers.optimizely.com/content-management-system/v1.5.0-content-delivery-api/docs/customizing-content-delivery-api-for-edit-view. However the example that is provided wont work since HttpContextContextModeResolver that it uses checks for values in the current request that indicates that the request is made to the cms edit mode.
   This will never be true when you are using Content Delivery API to fetch the content since the request is made to /api/episerver/v3.0/content/... and not /episerver/cms/...
   In my opinion, Optimizely should have a built in way of previewing unpublished content delivered by Content Delivery API or… more

   3 votes

   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  ·  Integration / APIs  ·  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. Language codes in page tree (navigation and in page header menu are not the same

   If you in admin change the "Web Address Prefix" for languages the editor interface uses different language codes in different locations. In the page tree navigation it uses the language code but on the page header of the page the "Web Address Prefix" is used.
   This confuses the editors. See attachments.

   3 votes

   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  ·  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

3. Granular Access Rights for CMS Settings Area

   In the Settings area anyone with the "CMSAdmin" or "Content Admins" has access to the full rights to edit anything in here.
   We should be able to set granular rights to these function areas for example if I want a specific user group to be able to make updates to Content Types but not Manage Website and Access Right this should be possible

   3 votes

   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  ·  Login, Roles & Permissions  ·  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

4. Full Project View

   Allow for a full list view of all project details, including tasks and workflow steps. It's hard to review all the work needed for a project when having to flip between each task to see the workflow steps.
   Something like this:
   | Task 1 | Start Date | End Date | Owner | Status |
   | Step 1 | Start Date | End Date | Owner | Status |
   | Step 2 | Start Date | End Date | Owner | Status |
   | Task 2 | Start Date | End Date | Owner | Status |
   | Step 1 | Start Date | End Date | Owner | Status |
   An alternative would be to allow to sort the board view by task and show workflow steps within each board.

   Allow for a full list view of all project details, including tasks and workflow steps. It's hard to review all the work needed for a project when having to flip between each task to see the workflow steps.
   Something like this:
   | Task 1 | Start Date | End Date | Owner | Status |
   | Step 1 | Start Date | End Date | Owner | Status |
   | Step 2 | Start Date | End Date | Owner | Status |
   | Task 2 | Start Date | End Date | Owner | Status |
   | Step 1… more

   3 votes

   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  ·  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

5. EPiServer.Forms.Samples uses out of data JQuery.UI with known vulnerabilities

   One of our customers is using the EPiServer.Forms.Samples library, mostly to facilitate content gating with the Forms Visitor Groups. During a recent penetration test the following was reported:
   We also observed the use of a known vulnerable version of jquery-ui at /Util/EPiServer.Forms.Samples/jquery-ui/jquery-ui.js which is known to have the following vulnerabilities
   CVE-2022-31160 (https://nvd.nist.gov/vuln/detail/CVE-2022-31160 : XSS when refreshing a checkboxradio with an HTML-like initial text label
   Recommendation
   Use the latest versions of the dependencies where possible. If it is not possible to update these, ensure the vulnerable components are not used.
   There does not appear to be an equivalent of the forms.config that would allow us to prevent the injection of jquery-ui.js for the EPiServer.Forms.Samples package.
   Can we please get an update for this package so that the out of date library is not used, and if possible, the capability to disable this from needing to be injected.

   One of our customers is using the EPiServer.Forms.Samples library, mostly to facilitate content gating with the Forms Visitor Groups. During a recent penetration test the following was reported:
   We also observed the use of a known vulnerable version of jquery-ui at /Util/EPiServer.Forms.Samples/jquery-ui/jquery-ui.js which is known to have the following vulnerabilities
   CVE-2022-31160 (https://nvd.nist.gov/vuln/detail/CVE-2022-31160 : XSS when refreshing a checkboxradio with an HTML-like initial text label
   Recommendation
   Use the latest versions of the dependencies where possible. If it is not possible to update these, ensure the vulnerable components are not used.
   There does not appear to be an equivalent of the… more

   3 votes

   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  ·  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

6. Automatic copy of database from production to preproduction

   Preproduction should resemble production. There should be an automatic function for copying the database from production to preproduction and keep the correct hostnames in preproduction. This should also be possible to schedule as preferred.

   3 votes

   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  ·  Implementation  ·  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. Allow container pages that don't generate a URL segment

   Some functionality cascades down the page tree, like approvals or permissions. Sometimes you want to group pages together so you can apply values and functionality to branches of pages, but these necessarily affects the URL, since any page generates a new URL segment.
   "Container" pages can't be accessed directly, but they still generate a URL segment, so they can't be transparently used for grouping content.
   It would be helpful to allow a type of container page that doesn't generate a URL segment. When ancestors are collected to form a URL for a descendant page, this type of page could simply be skipped and its segment omitted.

   Some functionality cascades down the page tree, like approvals or permissions. Sometimes you want to group pages together so you can apply values and functionality to branches of pages, but these necessarily affects the URL, since any page generates a new URL segment.
   "Container" pages can't be accessed directly, but they still generate a URL segment, so they can't be transparently used for grouping content.
   It would be helpful to allow a type of container page that doesn't generate a URL segment. When ancestors are collected to form a URL for a descendant page, this type of page could simply… more

   3 votes

   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  ·  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

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

   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

9. [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

   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

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

    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.

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

    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.

12. Ability to rename PaaS Instances to align with customer use cases

    Currently when Applications are provisioned, the application name is auto generated and not changeable. This makes it hard in the long term to align support tickets which align to a specific customer site/application, which delays support and contributes to errors. Creating the ability for these names to be changed will improve support and reduce confusion.

    3 votes

    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  ·  Other  ·  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. Ability to add custom CAA records in a managed clients zone in Optimizely Cloudflare account
    3 votes

    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

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

    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

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

    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

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

    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

17. Auto-translate

    I use Auto-Transalte a lot but I don't want the Name, URL and Reference to be translated automatically.

    When handling multiple language websites it is practical to keep the Name, URL & Reference in English.

    The URL I can change manually if necessary

    3 votes

    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  ·  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
    Gathering Feedback  ·  AdminTom Bramley (Senior Product Manager, Optimizely) responded

    Thank you for raising this feedback request. We will continue to gather feedback to assess demand for this functionality.

18. Site-specific Wastebaskets for multisite

    As of now all sites share the same Wastebasket in a multisite. We need site-specific wastbaskets so that only the editors with access to a site (and wastebasket) can go to the site-specific wastebasket and delete content. Closing in to almost 100 sites with extreme amounts of data, our wastebasket is not possible to navigate - even for admins.

    2 votes

    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  ·  Implementation  ·  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

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

    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!

20. Upload very large single files using cms

    People are needing to upload very large files, such as video files and are running into Cloudflare file size limits.

    Being able to upload a very large file into the storage blobs using the Deployment API and then being able to refer to it in the CMS may be a way to work around the size limits in Cloudflare.

    The problem trying to do this now is that uploading via the deployment API won't make it into the same container that the CMS is configured to read from. Also, usually when people add media, a reference in the DB is created so that when someone requests that media, there is a blob path to reach out to.

    People are needing to upload very large files, such as video files and are running into Cloudflare file size limits.

    Being able to upload a very large file into the storage blobs using the Deployment API and then being able to refer to it in the CMS may be a way to work around the size limits in Cloudflare.

    The problem trying to do this now is that uploading via the deployment API won't make it into the same container that the CMS is configured to read from. Also, usually when people add media, a reference in the DB is… more

    2 votes

    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  ·  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