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.
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).
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.
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.
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
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?
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
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.
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.
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).
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.
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.
is working on a reply...