Product: Sitecore MVC

  1. Async support

    Async controllers should be supported on Item controller and ControllerRendering level.

    164 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Improve Sitecore MVC Routing features

    Improve routing features relating to multi-site, attribute routing, relative routes.

    98 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Improve form handling

    Especially around multiple forms on a page. Perhaps better documentation/guidance around Sitecore MVC FormHandler.

    78 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  4. Area support

    Sitecore MVC should support MVC areas

    46 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Great news – we delivered Area support for Layouts, View Renderings and Controller Renderings in 8.1. We will expand on Area support in upcoming releases.

    Regards,
    Kern

  5. Provide sample items in MVC

    The Sitecore sample items are still in WebForms. For playground environments it would be nice to have them in MVC, or at least have them too (as a second choice).

    43 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Fix TempData weirdness

    Due to the context stack TempData is behaving different from standard MVC controllers/child controllers. Having ControllerRenderings exhibit child-action behaviour is a possible fix.

    31 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Improve HTTP status codes and exception handling

    E.g. improve Exception messages, access denied responds with 404... there may be others.

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Improve html extensions api to guide developers instead of ‘Magic Parameters’

    Add additional overloads to the Sitecore html extensions, for example:

    @Html.Sitecore().Rendering("{id}", "{datasource-id}");

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Ease of writing Unit Test in the Sitecore MVC framework

    The Sitecore MVC framework should be conducive enough for developers to write a unit test

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Fix caching issues

    Fix Stiecore MVC caching issues (Sitecore cache and OutputCache attribute).

    16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Provide a more granular exception handling mechanism

    If an unhandled exception occurs in a rendering, currently the action is to route the user to the error page. If this happens in the experience editor, there is the possibility for lost work. I would like to see some way of handling the error on a per rendering basis and determine what to do. This would allow us to have better control of the user experience when a component fails.

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Same controller name in different areas should be possible

    In Sitecore 8.1, there is native support for MVC areas. Let us assume I have two area, "Area1" and "Area2". In both of them I have a controller "MyController". Now I have a controller rendering definition item where I add as controller name "My" and as action "MyAction". I will resolve the area with a custom strategy by Sitecore.Context.Site. Now, when I add this controller rendering to an item in "Site1", then the controller in "Area1" should be resolved by Sitecore, and when I add the same controller rendering to an item in "Site2", then the controller in "Area2" should…

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  13. Form validation messages from Sitecore dictionaries

    Form validation can be set via Data Annotations. The validation message can be translated with .net Resources. It would be nice to have a similar way, but using Sitecore dictionaries for it.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  14. Ensure azure index name is valid

    To be able to have developer individual azure-search indexes it would be great if the CloudSearchProviderIndex not only switched out
    "_" to "-" but also med a toLower().

    What we tried to do was to patch in $(env:COMPUTERNAME)(id) , but since Azure wont support UpperCases in index name that didnt work.

    So therefore it would be great if CloudSearchProviderIndex nativly also made a toLower() for the CloudNameIndexName

    https://docs.microsoft.com/en-us/rest/api/searchservice/naming-rules

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add VaryByRoute Caching Option

    Much like we can vary by query string, it would be nice to vary HTML/output cache by a hash of the route data.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Improve Sitecore Modules stability when used with Sitecore MVC

    Currently there are some serious issues with the Sitecore Modules when used with Sitecore MVC(especially with WFFM). Like WFFM breaks the posting of custom forms, WFFM not correctly injected (they require their data source to be set manually) etc.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. MVC 'Areas' split-up under APP_Config/include

    can expect MVC 'Areas' split-up under APP_Config/include rather than having module level split up to manage config changes much easier.
    EX:
    App_Config
    Include
    Sitecore/*.config
    TenantA/*.config
    TenantB/*.config
    Global/*.config

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Product: Sitecore MVC

Categories

Feedback and Knowledge Base