Documents moved to a new category don't appear on web in the correct place

[Richard H.]

A document was updated in the DL. Part of the update was to assign it to a different category in the DL. Everything went through fine, but on the Silva CMS side the document was still appearing in the DL Listing that points at the old category, rather than appearing in the other DL Listing which was pointing at the new category.

This has since happened with a second unrelated document elsewhere in the DL.

We're certain that being able to move docs around in the DL was working fine in the past. We've checked the caching server (squid) and that doesn't appear to be the cause.

Any idea what's going on?

[Kit Blake (kitblake)]

Sorry, if it's not Squid, we have no idea what's going on. I'll add this to the consideration list for the next release.

[Richard H. (richard-hewison)]

Okay. We should have a list of new DL developments to bring to your attention in the near future.

--

Richard Hewison
IT Documentation (ISD)
ex. 3810
>>> On 27/04/2010 at 12:22, Kit Blake <email address hidden> wrote:
> Sorry, if it's not Squid, we have no idea what's going on. I'll add this
> to the consideration list for the next release.
>
> ** Tags added: wishlist
>
> --
> Documents moved to a new category don't appear on web in the correct place
> https://bugs.launchpad.net/bugs/570605
> You received this bug notification because you are a direct subscriber
> of the bug.

[Sylvain Viollon (thefunny)]

This was indeed a bug. I committed a fix in Products.OAICore, to update the setSpec values of a record while updating it. (categories are implemented via setSpec).