Comment 3 for bug 254576

Revision history for this message
Ross Patterson (rossp) wrote : Re: [Bug 254576] [NEW] CMFCore.exportimport.content doesn't index results of .properties

Ross Patterson <email address hidden> writes:

> Tres Seaver <email address hidden> writes:
>
>> Ross Patterson wrote:
>>> Public bug reported:
>>>
>>> In CMFCore/exportimport/content.py:201, the title and description for
>>> the newly created content are set but nothing is done to reindex the
>>> objects so that the catalog will reflect the new values. It seems that
>>> the solution might be as simple as adding "content.reindexObject()"
>>> after "content.setDescription(description)".
>>
>> -1. Generally speaking, doing incremental indexing during bulk
>> operations is a lose: I would rather disable even the minimal "after
>> add" indexing than add more of it.
>
> But then how can I write a profile that will make some small content
> changes to a large sire that won't require a lengthy catalog reindex?

For example, I ran into this problem making a simple profile for a
customer that setup the portal tabs/global sections. Without the
reindexing, running the profile means the global sections display with
the object ids instead of titles. I assume this would also affect the
navigation portlet.

Ross