Copied to clipboard

Flag this post as spam?

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


  • John Bergman 429 posts 982 karma points
    Dec 17, 2018 @ 21:50
    John Bergman
    0

    Error importing: values of parentId and docNode/@parentID are different

    Anyone seen this, or know how to correct it? The health checks do not show any issues related to integrity

    enter image description here

  • Kevin Jump 1483 posts 9546 karma points MVP 3x c-trib
    Dec 18, 2018 @ 09:43
    Kevin Jump
    0

    Hi John,

    looks like the error is coming from deep in the cache update when umbraco publishes the content I think its happening on the publish of content when uSync syncs the content item.

    The error says it really for some reason the Parent ID of the content is not the same

    within uSync the parent is worked out below:

    When content is imported the parent of the content in the root of the folder is passed down for all elements beneath it.

    but when an item is loaded the .config file will have a parentGuid of the actual parent the node had - this guid is used to lookup the "real" parent (often if not almost always the same as the folder). - and then set on the node.

    when the item is created this parent Value is used or when the content already exists then the parentId is set before the content is saved (with content it's a two step sync - the publish happens in the second pass).

    If things have moved about those two ids can be out of sync (so the parent folder not be the parent of the content item) but everything should still work.

    as a start i would turn up logging of usync (in log4net.config)

    <logger name="Jumoo.uSync">
       <level value="DEBUG" />
     </logger>
    

    and see if you can see which node is throwing the error. then see if the parent nodes have been mangled in any way

  • John Bergman 429 posts 982 karma points
    Dec 19, 2018 @ 17:08
    John Bergman
    0

    Hi Kevin, I also see this

    Error: undefined - undefined

    This appears to happen when this is present in the log 17:02:03.538 INFO
    Our.Umbraco.FileSystemProviders.Azure.AzureBlobFileSystem

    No file exists at 1137/img_3689.jpeg. 17:02:03.538 ERROR
    Umbraco.Core.Media.UploadAutoFillProperties

    Could not populate upload auto-fill properties for file "1137/img_3689.jpeg". System.ArgumentException: Value of 'null' is not valid for 'stream'. at System.Drawing.Image.FromStream(Stream stream,

  • John Bergman 429 posts 982 karma points
    Dec 19, 2018 @ 19:07
    John Bergman
    0

    Moving this over to GitHub; I have a couple of reproducible bugs.

Please Sign in or register to post replies

Write your reply to:

Draft