Copied to clipboard

Flag this post as spam?

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


  • Michael Hoes 6 posts 36 karma points
    Feb 28, 2013 @ 12:47
    Michael Hoes
    0

    Content saved in wrong properties

    I have a very weird problem. Sometimes content gets saved in the wrong property. For example, the text of the property introText gets saved in thumbnailMediaId. We don't now when this happens.

    I also have to tell that we have a custom datatype to create relations, and when pushing the save/publish button, a specific property of all the related items get updated to.

    Does anyone experienced the same problem? We are using umbraco 4.7. 

  • Sander Houttekier 114 posts 163 karma points
    Feb 28, 2013 @ 13:18
    Sander Houttekier
    0

    does this happen every time, or totally random
    as we have had issues like that, but more due to the fact that several people are working and publishing nodes in the same backend.

    and the problem was with 2 publish calls being executed at the same time in which writing to the database got messed up and mixed the 2 nodes together.

    this is not version related and can happen in every version of umbraco.

    but your description made me think you have something 'similar' yet different going on.
    could you specify if this is a regular thing, (every time you save, field x is saved in field y etc?)

    *edit* is there anything special about the documentType you try to save?

    are there actionHandlers working on pre or post save / publish?
    are there custom datatypes present on the documentType?

    best regards
    Sander 

  • Michael Hoes 6 posts 36 karma points
    Feb 28, 2013 @ 13:48
    Michael Hoes
    0

    So, if different persons are editing content at the same time, it is possible that documents get corrupt?

    It is by the way totaly random. We even don't now when this occures. Our customer noticed that his documents were messed up sometimes.

    There is 1 afterpublish event, that updates a related node in an other language. But that couldn't be the problem because not all documents that were messed up don't have a related language node.

    It is not only one kind of documenttype, it are several.

    The only extra thing we have is a custom datatype to create relations between documents. When pushing save or publish, a specific property of all the related items gets updated.

     

  • Sander Houttekier 114 posts 163 karma points
    Feb 28, 2013 @ 14:07
    Sander Houttekier
    100

    I can say, we have had it before,

    and yes you can have corrupt nodes when you launch 2 publish or save calls at exactly the same time (this is very rare) so if you say you have it sometimes, it might likely be something else because having 2 statments writing to the database at EXACTLY the same time is very rare.

    unless we're talking about mass publish calls, if you duplicate a whole language with several nodes below it, and start publishing those (with children), it is more likely that 2 of those might be of influence to one another.

    however, there is not really anything you can do about that, it is how umbraco is build and a common pitfall with heavy database active websites. 
    there are probably fixes for that but this something to be fixed in the very core of umbraco.

    since we had the occurance once, and almost 1.5 years ago, we never had it again, even with the 4 people active on the backend of that umbraco daily. so it is rare to have this bug more than once. 

  • Michael Hoes 6 posts 36 karma points
    Feb 28, 2013 @ 14:33
    Michael Hoes
    0

    Thanks that would likely be the problem. We will look more deeper in to this problem, and will try to find a workaround.

Please Sign in or register to post replies

Write your reply to:

Draft