Silva dl-cherry caching/update problem?

[Richard H.]

I mistakenly moved the dl-cherry object into the Zope root, thinking that Silva instances would inherit it. Of course, they don't (as it isn't a mandatory object) and they should each have their own (which I presume can be copied between Silva instances?).

Anyway, the point is that our test dl (staff) didn't notice that the dl-cherry object was no longer where it should have been. It continued to work (displaying cherry-picked documents) regardless!

What are we supposed to do to make Silva realise things have changed, or is this a caching problem of some kind with Silva?

[Kit Blake (kitblake)]

What do you mean by mandatory in "they don't (as it isn't a mandatory object)". I haven't tried this myself, but I think it should work.

[Richard H. (richard-hewison)]

I'm guessing that the reason why Silva doesn't inherit a 'dl-cherry' object from the Zope root is because the object itself can be named anything and it also isn't a mandatory object (i.e. you don't have to have one at all).

If you place a dl-cherry object in the Zope root, then when you try and access it in the SMI, Silva doesn't know its there. However, a Silva instance that was using that dl-cherry object (before it was moved to the Zope root) continues to work even though it now shouldn't.

>>> On 21/04/2008 at 11:12, Kit Blake <email address hidden> wrote:
> What do you mean by mandatory in "they don't (as it isn't a mandatory
> object)". I haven't tried this myself, but I think it should work.
>
> --
> Silva dl-cherry caching/update problem?
> https://bugs.launchpad.net/bugs/220161
> You received this bug notification because you are a direct subscriber
> of the bug.

[Kit Blake (kitblake)]

This doesn't sound right (but you've seen it happen). Acquisition should be working. We'll have to play with it and see what exactly is going on.