Thanks for the help, we think we've worked out what was happening.No default publication target was set and the first publication target created appears to have taken on that role. When the second and third targets were added, the original target was still maintaining control. Problem was, that location was receiving files from two different projects on different servers and that seems to have caused CMS to think it had to clean up the other locations when it found differences in the original location. We're not 100% sure that's what was happening and by setting a default publication target and removing the original redundant one we still can't test it as we're not willing to take the risk of a production site being deleted without warning. Next project though will take the above into account and hopefully the deletions will not occur.
Cheers, Gavin 2009/8/5 kimdezen <[email protected]> > > Actually.. come to think of it, i think it would 'delete' all of the > files from the server only when you swap default publication targets.. > > Anyways.. my advice is to be careful using this option. > > Kim > > > kimdezen wrote: > > Hi Gavin, > > > > Its been a while since ive used this option (since it caused us issues > > in the past!!!) > > > > From memory, it did actually physically delete the files from the > > server.. however we noticed that if the project contained more than 1 > > publishing target (say you had a connection to a staging/dev server) - > > it would delete ALL pages from all other targets that were not the > > 'default' target. > > > > I dont know if this has been fixes/addressed in later versions (i.e. > > 7.5 - 9 etc).. but im not game to give it another go!!! > > > > Cheers, > > Kim > > > > > > On Aug 5, 7:13 am, Gavin Cope <[email protected]> wrote: > > > Actually, come to think of it, you've triggered something in my memory > from > > > many years ago and maybe seeing the file in the location where the > files > > > were being ftp'ed too. Time to hunt down some ftp account details to > check > > > the server. > > > > > > 2009/8/5 Gavin Cope <[email protected]> > > > > > > > Hi Stefan, > > > > Cool, that's good news. Do you know if the file is transferred across > to > > > > the published site or stored on the CMS server? > > > > > > > Cheers, > > > > > > > Gavin > > > > > > > 2009/8/4 stefan.popp <[email protected]> > > > > > > >> Hi Gavin, > > > > > > >> if you have activated "Create delete list" in the general settings > in > > > >> your cms project a physical file will be created when publishing via > > > >> (s)ftp. I do not know, if the file is created, when publishing to a > > > >> directory. > > > > > > >> Regards, > > > >> Stefan > > > > > > >> On Aug 4, 12:09 pm, Gavin Cope <[email protected]> wrote: > > > >> > Hi All, > > > > > > >> > Just wondering if anyone is an expert when it comes to the CMS > delete > > > >> list > > > >> > functionality. I know when publishing to LiveServer, it actually > creates > > > >> a > > > >> > file that it sends to LiveServer for deletions. But what about > when > > > >> doing > > > >> > directory publishing or (s)ftp publishing? Is a physical file > created or > > > >> is > > > >> > it only "virtual" and/or stored in the database and thus not > accessible > > > >> > after a publish? > > > >> > The reason I'm trying to find it is we have - what appears to be - > a > > > >> random > > > >> > situation where a publish in one of our projects will trigger a > full > > > >> site > > > >> > deletion despite all the pages still existing in the project tree. > > > >> Needless > > > >> > to say, this would be a bad, bad thing to happen to a production > web > > > >> site. > > > > > > >> > Cheers, > > > > > > >> > Gavin > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/RedDot-CMS-Users?hl=en -~----------~----~----~----~------~----~------~--~---
