Copied to clipboard

Flag this post as spam?

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


  • Steve Crook 28 posts 160 karma points
    3 days ago
    Steve Crook
    0

    Multiple "Cleanup disabled for version" messages after save

    I've got a site that's translated into 8 languages, which I upgraded recently from Translation Manager 10.3.0 to 10.6.1. Since then, every time I save a page, no matter how many language variations are saved, I get 8 messages in the page history saying "Cleanup disabled for version". I think this is probably something to do with this change in the release notes for 10.6:

    Preserve versions of content (prevent cleanup) that are used in translations

    Two questions:

    1. I have cleanup enabled, so why is TM disabling cleanup? I'm sure there's a good reason but I'd like to understand why.
    2. Why is it logged 8 times?
  • Kevin Jump 2332 posts 14859 karma points MVP 8x c-trib
    3 days ago
    Kevin Jump
    0

    Hi,

    Yes, cleanup is disabled by translation manager because it uses the version of the conent as it was sent when putting content back in.

    This is used so we can preserve the order and layout of things when they come back.

    If for example you send some grid (gird or block grid) content to translation then there will be a number of blocks send and they will be in a certain layout.

    The layout and configuration of the blocks is not part of the translation (thats just the text really).

    If inbetween sending the content for translation and it coming back someone changes the block layout then when the content comes back we wouldn't know where to put it all, so in order to put it back reliably we need to be able to reference the layout at the point the translation was sent, so this is done with the version.

    to stop the version going it is marked as cleanup disabled (internal umbraco flag).

    I think it happens 8 times because each language is processed independently of each other, (to create the 8 jobs) - so each one 'protects' the version - i don't think its got like 8 times protection :) just the one.

  • Steve Crook 28 posts 160 karma points
    3 days ago
    Steve Crook
    0

    Thanks Kevin for the explanation.

    All that logging is a bit ugly - would it be possible to protect the version only if it isn't already protected? Otherwise I could look at running a task to delete from the umbracoLog table periodically.

Please Sign in or register to post replies

Write your reply to:

Draft