+1-888-365-2779
Try Now
More in this section

Forums / Developing with Sitefinity / MVC routing in 6.1

MVC routing in 6.1

17 posts, 1 answered
  1. Gary
    Gary avatar
    28 posts
    Registered:
    16 May 2012
    24 Jul 2013
    Link to this post
    Hi,

    My custom MVC widgets have stopped routing properly in Sitefinity 6.1.

    I can't seem to get any routing to work at all now on custom MVC widgets.
    Here is a test action snippet from my controller:
    public ActionResult test()
    {
        return View("test");
    }

    and in my view, I'm simply testing:
    <p>It works!</p>

    I made a hybrid page called 'sample' and added the controller to it.

    When I go to "/sample/test/" - I get a 404!

    Any idea what could have changed to cause these issues? 

    Thanks,

    Gary
  2. Evan
    Evan avatar
    5 posts
    Registered:
    02 Jun 2009
    24 Jul 2013
    Link to this post
    Bump.

    I ran into this exact same issue. I ran a test with a really small demo project that I had created. The routing worked just fine and I was able to load content via an ajax call when the project was still using v6.0 but as soon as I upgraded the project to 6.1, the exact same route that had worked 10 minutes before now returns a 404.
  3. Stanislav Velikov
    Stanislav Velikov avatar
    1113 posts
    Registered:
    05 Dec 2016
    29 Jul 2013
    Link to this post
    Hello,

    I have reproduced the problem and I am still investigating the issue occurring. I will update you further when I have more information on the causes and how to fix

    Regards,
    Stanislav Velikov
    Telerik
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  4. Gary
    Gary avatar
    28 posts
    Registered:
    16 May 2012
    30 Jul 2013 in reply to Stanislav Velikov
    Link to this post
    Thanks Stanislav.

    Do you know when we can expect an update, as I'm currently running a project that I would like to launch on 6.1, but I plan to go live shortly.

    Many thanks,

    Gary
  5. Kevin
    Kevin avatar
    8 posts
    Registered:
    11 Dec 2012
    02 Aug 2013
    Link to this post
    I would also like an update on this issue please as it is critical to our sites and we have already deployed to our test environments and hit this issue.
  6. Victor
    Victor avatar
    94 posts
    Registered:
    15 Jun 2011
    02 Aug 2013
    Link to this post
    Any update on this?
  7. Gary
    Gary avatar
    28 posts
    Registered:
    16 May 2012
    05 Aug 2013
    Link to this post
    Hi,

    My renewal is due very shortly and I'm in the progress of remaking the website. Please advise if Sitefinity is going to be fit for use, or if I should look for alternative solutions?

    I'm spending a lot of money to go 2 weeks with such a major issue without a solution.

    Gary
  8. Sam
    Sam avatar
    3 posts
    Registered:
    19 Jul 2013
    05 Aug 2013
    Link to this post
    Hi,

    We too are urgently looking for a fix for this. Currently we are having to rewrite large chunks of our site to get round this major issue.

    Please update asap.

    Sam
  9. Ryan
    Ryan avatar
    2 posts
    Registered:
    23 Jul 2010
    05 Aug 2013
    Link to this post
    This is a huge issue for me as well.  An ETA on the fix would be appreciated.
  10. Victor
    Victor avatar
    94 posts
    Registered:
    15 Jun 2011
    05 Aug 2013
    Link to this post
    A ballpark would be great.

    Should we start rewriting code?
  11. Kevin
    Kevin avatar
    8 posts
    Registered:
    11 Dec 2012
    05 Aug 2013
    Link to this post
    Would really appreciate an official response on this.
  12. Stanislav Velikov
    Stanislav Velikov avatar
    1113 posts
    Registered:
    05 Dec 2016
    06 Aug 2013
    Link to this post
    Hello,

    The issue occurring is investigated at our end, but so far we don`t have a solution. We are looking to getting it to work as soon as possible and based on the solution will act in a way to provide a feasible fix for everyone encountering the issue.

    Regards,
    Stanislav Velikov
    Telerik
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  13. Stanislav Velikov
    Stanislav Velikov avatar
    1113 posts
    Registered:
    05 Dec 2016
    06 Aug 2013
    Link to this post
    Hi,

    We have found the cause of the problem and found a workaround to the issue that can be applied trough a setting, refer to this KB article to apply the workaround which will fix the issue.

    Regards,
    Stanislav Velikov
    Telerik
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
    Answered
  14. Gary
    Gary avatar
    28 posts
    Registered:
    16 May 2012
    06 Aug 2013 in reply to Stanislav Velikov
    Link to this post
    Thanks Stanislav - This seems to have fixed it!
  15. Sam
    Sam avatar
    3 posts
    Registered:
    19 Jul 2013
    07 Aug 2013 in reply to Stanislav Velikov
    Link to this post
    This also seems to be working for us too, thanks for the fix.

    Is this a permanent solution or will a patch be released in (for example) 6.2 which we should be aware of?

    Sam
  16. Victor
    Victor avatar
    94 posts
    Registered:
    15 Jun 2011
    07 Aug 2013
    Link to this post
    Are there ramifications for using "EnableBackwardCompatabilityForPagesUrls".
    Other than fixing this error, what is this setting used for?

  17. Stanislav Velikov
    Stanislav Velikov avatar
    1113 posts
    Registered:
    05 Dec 2016
    12 Aug 2013
    Link to this post
    Hello,

    The setting "EnableBackwardCompatabilityForPagesUrls" resolves url parameters from the url. Because the navigation to an action when posting a form goes to site.com/page/actionName where actionName is the url parameter this setting ensures this parameter is taken into account.
    Without the settings the request made to this url parameter was returning 404. The setting is a workaround to make sure url parameters are taken into account.

    There will be a fix for this to return the behavior for MVC routing that was present in sitefinity 6.0, the fix is aimed for sitefinity 6.2 release. We don`t foresee an issue occring resolving url parameters for page urls.

    Regards,
    Stanislav Velikov
    Telerik
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
17 posts, 1 answered