Sign in Register
Go to solution
Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Thomas Beckert 193 posts 469 karma points
    May 14, 2017 @ 21:04
    Thomas Beckert
    0

    DependencyHandler Error when debug=false

    Hi, everyone,

    I upgraded from 7.5.13 to 7.6.1 and now, if I run my page in debug=false mode, my custom section throws an error, says that the controller is not found and an error in the DependencyHandler occured.

    If I set debug=true, everything works.

    I did some investigation on the web, the error seems not to be very new, but all the suggested solutions did not work for me.

    1. cleared the cache folders (I really killed and deleted all of them)
    2. adding my Domain to the bundleDomains in the ClientDependency.config
    3. Increasing the Version Number in CD
    4. Increasing the length of a request in the web.config
    5. Winmerge web.config of 7.6.1 with my custom one
    6. ClientDependency.config referred right in web.config
    7. System.Web.Http Assemby is reffered in web.config
    8. Up-to-Date binding-redirect of MVC

    So I'm running out of ideas. Any suggestions from the community?

    Cheers,

    Tom

    Copy Link
  • René 327 posts 852 karma points
    May 26, 2017 @ 13:13
    René
    0

    Hi Tom

    Did you find any solutions on this one.. I have the same problem.

    René

    Copy Link
  • Thomas Beckert 193 posts 469 karma points
    May 26, 2017 @ 13:27
    Thomas Beckert
    0

    Unfortunatelly no. Still have this issue.

    Copy Link
  • Amit 10 posts 81 karma points
    Jun 01, 2017 @ 08:47
    Amit
    0

    Hey Thomas,

    Our guys found the issue, when we tried to figure it out we came across your post, now that we found it - we had to get back to you to try and help :)

    Do you by any chance use Areas in your site? :)

    Copy Link
  • Thomas Beckert 193 posts 469 karma points
    Jun 01, 2017 @ 08:56
    Thomas Beckert
    0

    Hi, Amit,

    what do you mean with areas? We have custom section, yes. :)

    Copy Link
  • Amit 10 posts 81 karma points
    Jun 01, 2017 @ 09:01
    Amit
    0

    then I believe we can help you:

    https://our.umbraco.org/forum/using-umbraco-and-getting-started/85936-umbraco-761-backoffice-not-working-under-iis#comment-272934

    read the last comment, the issue we've experienced is when registering custom routes (regardless of areas or custom sections) there is an issue when trying to register to the domain name without any prefixes - i.e 'www.yourdomain.com/' instead of - 'www.yourdomain.com/MyCustomSection'

    try to add the ignoreRoute method when registering your custom section/area.

    and please, let us know if that fixed the issue.

    Good luck

    Copy Link
  • Thomas Beckert 193 posts 469 karma points
    Jun 01, 2017 @ 09:08
    Thomas Beckert
    0

    We add our custom section by the applications.config file. So there is no way to say "IgnoreRoute", I guess? Maybe we should transfer the section generation to C# code?

    Copy Link
  • Amit 10 posts 81 karma points
    Jun 01, 2017 @ 10:24
    Amit
    0

    yes, you add them with application config, but do you also register those routes somewhere? we do that in our custom ApplicationEventHandler..

    by calling RouteConfig.RegisterRoutes and explicitly register our custom section controllers (we use standard mvc controller-views for our custom section, not angular)

    Copy Link
  • Thomas Beckert 193 posts 469 karma points
    Jun 01, 2017 @ 14:35
    Thomas Beckert
    0

    Hi, No, we don't register our routes somewhere. We just call this now:

        namespace umbHbiG.Klassen.CustomSections
{
    [Application("ReservierungsSection", "Rerservierung", "icon-food", 15)]
    public class TischreservierungsSection : IApplication
    {

    }
}

    We use angular in our custom sections. So maybe your fix will not work with us?

    See solution in the next post.

    Copy Link
  • Thomas Beckert 193 posts 469 karma points
    Jun 15, 2017 @ 19:39
    Thomas Beckert
    0

    Finally, finally, I found the error.

    A student of mine coded some AuthorizedApiController, that are inherits from "UmbracoAuthorizedJSONController".

    I changed all that to "UmbracoAuthorizedApiController" -> Error gone, me happy. :)

    Thanks anyway to all of you for your support.

    Copy Link
Please Sign in or register to post replies

Write your reply to:

Draft