Copied to clipboard

Flag this post as spam?

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


  • Lee 1130 posts 3088 karma points
    Jun 17, 2013 @ 10:24
    Lee
    0

    Macro UI Error After Upgrade?

    I have a site I upgraded a good few months ago to 4.11.7. And its been fine. However, today I have the need to create a Macro - Something I hadn't done since the upgrade.

    I can create the macro, but when it tries to show the macro edit UI in the umbraco admin I get this error below. Also this error appears for ALL macros if I try to view them.

    Any ideas?

    Object reference not set to an instance of an object.

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

    Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

    Source Error: 

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace: 

    [NullReferenceException: Object reference not set to an instance of an object.]
       Umbraco.Web.UI.Umbraco.Developer.Macros.EditMacro.PopulatePartialViewFiles() +694
       System.Web.UI.Control.LoadRecursive() +70
       System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3177
    


    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.17929
  • Jamie Howarth 306 posts 773 karma points c-trib
    Jun 17, 2013 @ 10:44
    Jamie Howarth
    0

    Have you got a "Views" directory in your installation?

  • Lee 1130 posts 3088 karma points
    Jun 17, 2013 @ 10:49
    Lee
    0

    Yep, and within that I have Partials & MacroPartials folder.

  • Richard Terris 273 posts 715 karma points
    Jun 17, 2013 @ 11:08
    Richard Terris
    0

    Long shot but what's the default rendering engine set as?

  • Richard Terris 273 posts 715 karma points
    Jun 17, 2013 @ 11:09
  • Lee 1130 posts 3088 karma points
    Jun 17, 2013 @ 11:10
    Lee
    0

    Currently set as follows

      <templates>

        <useAspNetMasterPages>true</useAspNetMasterPages>

        <defaultRenderingEngine>WebForms</defaultRenderingEngine>

      </templates>

  • Lee 1130 posts 3088 karma points
    Jun 17, 2013 @ 11:12
    Lee
    0

    Thanks have posted on that thread too.

  • Richard Terris 273 posts 715 karma points
    Jun 17, 2013 @ 11:13
    Richard Terris
    0

    It looked like the owner of that thread resolved the issue? That was the only reason I posted the link

    Having read what resolved it I doubt it has anything to do with the rendering engine but I'd try Mvc anyway just in case?

  • Lee 1130 posts 3088 karma points
    Jun 17, 2013 @ 11:18
    Lee
    0

    I can't set it to MVC as the default engine needs to be webforms. I'm not using MVC in this site as its an old site thats just had umbraco upgraded.

  • Richard Terris 273 posts 715 karma points
    Jun 17, 2013 @ 11:19
    Richard Terris
    0

    Ah - sounded like a mvc related error in the stack trace.

    But I'd hoped the other thread would have solved it for you.

    Sorry it didn't :)

  • Lee 1130 posts 3088 karma points
    Jun 17, 2013 @ 11:25
    Lee
    0

    No worries. I'm not 100% sure what the person did to resolve it in the other thread. There is no 'EditMacro' dll in the source that I can see? So not sure what they mean?

  • Richard Terris 273 posts 715 karma points
    Jun 17, 2013 @ 11:42
    Richard Terris
    0

    Only reference to editMacro I can see is a file called \umbraco\dialogs\editMacro.aspx

     

  • Stefan Kip 1614 posts 4131 karma points c-trib
    Jun 17, 2013 @ 11:53
    Stefan Kip
    0

    When I run into an issue which occurs in umbraco itself, I usually open the umbraco source solution in VS and attach the debugger to my w3wp process, so I can see exactly why the error occurs.
    I've tried to reproduce this error in two umbraco websites; v4.11.8 and v4.11.9, both sites exist for a while now (been upgraded multiple times, somewhere from 4.0.x), but I didn't run into this issue.

  • Lee 1130 posts 3088 karma points
    Jun 17, 2013 @ 12:07
    Lee
    0

    Managed to resolve this. I just upgraded everything to the latest v4.X or Umbraco and it all seems to have kicked to life again :/

Please Sign in or register to post replies

Write your reply to:

Draft