Red Hat Bugzilla – Bug 117393
RickshawPublishAPIUpgrade doesn't run any content type initializers
Last modified: 2007-04-18 13:03:50 EDT
Description of problem:
As a result of bug 117390, the RickshawPublishAPIUpgrade manually runs
the CMS initializer before doings its work. This, however, means that
none of the content item/asset initializers will have been run when
the republishing takes places. One consequence of this is that none of
the content ype speciifc search metadata XML generation rules will be
registered & thus the search indexes will be populated with garbage.
In other cases the publish may not even complete if the content item /
asset requires that a custom DomainObjectInstantiators be present -
for example the 'Address' content type requires a custom instantiator
for the ISOCode object.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
The RPAPIUpgrade#main method needs to run all the database-registered
initializers. Adding to blocker list.
Fixed a while ago now.