Hello Willem, Well, it keeps being a 'bug' obviously, but as a work around this is a perfect solution (and I think how everybody uses the repository, for example our cms). So, if you agree working like this with it, it might be fixed in the future. It obviously has to do with the queueing of the indexing for the deletions and the puts, but is also might be a little tricky to fix (think now the 'new' queue is a separate one from the 'remove' queue, and then I have to know whether first a remove was and then a put for one document, or first a put and then a remove, obviously, quite a big difference)
Anyway, since most people just use a put, we never found this issue. Great you can work with it by deleting the delete :-) Regards Ard > > > Ard, > We did another test by removing the DELETE altogether, which > worked fine. So if we PUT the new file directly we don't have > any problem on the repository side. > Thanks for helping out. > Willem > > -- > View this message in context: > http://www.nabble.com/FW%3A--HippoRepos-dev--multiple-dasl-sea > rch-results-onthesamerepository-entry-tp19608500p19608981.html > Sent from the Hippo CMS development public mailinglist > mailing list archive at Nabble.com. > > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > > Searchable archives can be found at: > MarkMail: http://hippocms-dev.markmail.org > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
