Copied to clipboard

Flag this post as spam?

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


  • Ronni 2 posts 22 karma points
    Feb 12, 2012 @ 05:54
    Ronni
    0

    Sudden error when creating document types

    HelloIve been using umbraco the last two days trying to learn from the CMS. However ive had encountering this error when i try to add my own document type, which gives me an error saying; "Object references not set to an instance of an object".

    Stack trace gives me the following output:

    [NullReferenceException: Object reference not set to an instance of an object.]
       umbraco.controls.ContentTypeControlNew.setupInfoPane() +545
       umbraco.controls.ContentTypeControlNew.OnInit(EventArgs e) +61
       System.Web.UI.Control.InitRecursive(Control namingContainer) +140
       System.Web.UI.Control.InitRecursive(Control namingContainer) +311
       System.Web.UI.Control.InitRecursive(Control namingContainer) +311
       System.Web.UI.Control.InitRecursive(Control namingContainer) +311
       System.Web.UI.Control.InitRecursive(Control namingContainer) +311
       System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +480

    Screenshot: http://img401.imageshack.us/img401/8828/documenttypeserror.png

    Could the umbraco database be corrupted or something?

  • Jan Skovgaard 11280 posts 23678 karma points MVP 11x admin c-trib
    Feb 12, 2012 @ 21:41
    Jan Skovgaard
    0

    Hi Ronni and welcome to the community :)

    It's hard to tell what might be the cause of this - have you manipulated the database directly or only through Umbraco? And do you by any chance have provided some weird characters on the alias name of the shown document type? If the alias is named something like "-Test" (without the quotes) it can mess things up.

    Looking forward to hear more about this issue.

    /Jan

  • Ronni 2 posts 22 karma points
    Feb 13, 2012 @ 12:31
    Ronni
    0

    Hi Jan

    Thanks for the reply. I have only been messing around within the Umbraco CMS itself, not the database. Thats why ive been curious as to why this error occured to me. Ive had some duplicates of macroes and document types of the same name, that i might have moved or deleted - perhaps this could be making an issue, if the document type(s) is trying to point to a nonexistant macro?

    Ive decided to start from scratch again and will be paying more attention as if something like this happens again :-)

Please Sign in or register to post replies

Write your reply to:

Draft