Yes the target folder exists. Nope, I dont expect it to be marked as published - I'm looking at the target folder with webdav client and not seeing the replication output.
I'll look at the logs to see if that has any clues. Ta - Tim Taylor JTeam On Tue, 2008-06-17 at 16:11 +0200, Bartosz Oudekerk wrote: > toolman wrote: > > Hey guys; > > > > Can anyone explain this odd behavior. I set up a replication that is > > internal; meaning that it reads and writes to the same repository (in a > > different location, I know, no cycles else replication would get into a > > nasty loop) > > eg: > > > > <replicator uri="/files/default.preview/content/pp"> > > <location> > > <host>localhost</host> > > <port>60000</port> > > <user>systemuser</user> > > <password>pass</password> > > <rootpath>/default</rootpath> > > <path>/files/default.www/content/pp</path> > > <createparents>true</createparents> > > > > <!-- retry if the http method fails --> > > <retrycount>10000</retrycount> > > <retrydelayseconds>3</retrydelayseconds> > > > > <!-- timeout settings --> > > > > <connecttimeoutseconds>30</connecttimeoutseconds> > > <sockettimeoutseconds>180</sockettimeoutseconds> > > </location> > > </replicator> > > > > this works fine for any item I write using the Java API to > > preview/content/pp, but I was expecting content in the folder to > > "auto-publish" - every save in the CMS to that folder, even with > > unpublished content, should trigger a replication - but it doesnt! > > > > Anyone know why the CMS is suppressing the replication? > > Does the directory /files/default.www/content exist? IIRC createparents > only works for directories below that point. > > And, are you sure they don't get replicated? If you replicate this way, > the CMS won't show the document as published, so you need to check the > repository directly. Also if the replication fails, I'd expect to see > something in the repository logs. > > Regards, ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
