Copied to clipboard

Flag this post as spam?

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


  • Daniel 4 posts 24 karma points
    Feb 23, 2015 @ 02:45
    Daniel
    0

    Duplicate content items

    Our umbraco website which uses usync is getting lots of duplicate content items.

    The usync folder would contain a node for Home but in the CMS we'd see

    • Home
    • Home (1)
    • Home (2)

    They seem to be created on startup and don't appear in the usync files on disk.

    How can I prevent them from being created?

  • Kevin Jump 1431 posts 9167 karma points MVP 3x c-trib
    Feb 24, 2015 @ 10:30
    Kevin Jump
    0

    Hi,

    I would be supprised if uSync is creating the content nodes. - uSync has no code to create content nodes in it. 

    uSync.ContentEdition does - but it requires the .def files to know what to call stuff (so files in /uSync/Content/) 

    Have you got Content Edition installed? (look for jumoo.usync.content in the bin folder)  ? 

    K

     

  • Daniel 4 posts 24 karma points
    Mar 03, 2015 @ 05:31
    Daniel
    0

    Yes jumoo.usync.content is installed, we are using it to deploy content. The idea was to create content in dev and use usync do deploy everything to prod.

  • Vivek 3 posts 23 karma points
    Mar 11, 2015 @ 17:53
    Vivek
    0

    Is the duplicating media items issue a result of using usync content edition as well?

    There are duplicating media items in addition to duplicating content nodes for me.

  • Kevin Jump 1431 posts 9167 karma points MVP 3x c-trib
    Mar 11, 2015 @ 18:15
    Kevin Jump
    0

    Yes - it's possible,

    check you are not blanking the uSync files in /appdata/temp/ as these are used to by uSync to keep track as to where a piece of content or media has come from.

    (everything is translated to and from the original GUID on the system something is created on).

  • Nicholas Westby 1890 posts 6308 karma points c-trib
    Mar 11, 2015 @ 18:22
    Nicholas Westby
    0

    Seems strange to store something like that in app_data/temp, as everything in that folder should be transient in nature (i.e., it wouldn't be terrible if it got deleted). It'd probably be fine to put it in app_data (e.g., in app_data/usync), but I would avoid putting it in the temp folder within there.

  • Kevin Jump 1431 posts 9167 karma points MVP 3x c-trib
    Mar 11, 2015 @ 23:47
    Kevin Jump
    0

    yeah, it sort of evolved - the importance of the file changed over development, but it's location didn't - also very annoyingly, i didn't make it an option in the settings.

    when i get some time to give content edition some TLC, it will almost certainly move, and hopefully less critical.

Please Sign in or register to post replies

Write your reply to:

Draft