Re: Correct Plone Catalog behaviour

Medur, if you haven't already done so,
can you please put up a How-To on this
on the fishbowl?

  (Medur) wrote:
> Problem:  Various copying procedures produce corresponding behaviour in 
> the Plone catalog. In the case where a plone site is copied the copied 
> portal_catalog object is rendered with a duplicate set of catalog 
> objects (old and new)
> 
> Solution:
> To refresh a portal catalog to the current state:
> 1. Clearing catalog in Advanced tab ( manage_catalogClear method )
> 2. Renaming copied site
> 
> This simple procedure guarantees a current version of the portal_catalog 
> in all cases.
> --------------------------------------------------------------------------
> This message is sent to you because you are subscribed to the mailing 
> list <VasudevaService-K9y3B4ipJAZZAIG4hdpdiNBPR1lH4CV8@public.gmane.org>.
> Vasudeva Service home: http://www.vasudevaservice.com/
> Browse list: nntp://news.gmane.org/gmane.org.misc.vasudeva-server.web
> List archive: 
> https://pop.vasudevaserver.org:13031/Lists/VasudevaService/List.html
> --------------------------------------------------------------------------
> 


--------------------------------------------------------------------------
This message is sent to you because you are subscribed to the mailing list <VasudevaService-K9y3B4ipJAZZAIG4hdpdiNBPR1lH4CV8@public.gmane.org>.