Bug 119327

Summary: UPGRADE: No entry in cms_section_template_map for MPA
Product: [Retired] Red Hat Enterprise CMS Reporter: Jon Orris <jorris>
Component: otherAssignee: Justin Ross <jross>
Status: CLOSED RAWHIDE QA Contact: Jon Orris <jorris>
Severity: medium Docs Contact:
Priority: medium    
Version: nightly   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-03-29 23:59:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 113496    

Description Jon Orris 2004-03-29 15:35:16 UTC 
Description of problem:
@41844/postgres

After the upgrade, there is no mapping in cms_section_template_map for
the MultiPartArticle. This results in MPAs using the default content
item template, which doesn't render it correctly; section links do not
work. See normal rickshaw vs. upgraded db below.


rickshaw=# select * from cms_section_template_map;
 mapping_id | section_id | type_id | template_id | use_context |
is_default
------------+------------+---------+-------------+-------------+------------
       1069 |         62 |    1063 |        1068 | public      | 1
(1 row)


upgrade=# select * from cms_section_template_map;
 mapping_id | section_id | type_id | template_id | use_context |
is_default
------------+------------+---------+-------------+-------------+------------
(0 rows)
Comment 1 Justin Ross 2004-03-29 22:47:14 UTC 
Addressed in perforce change 41881.  Note that this change means that
we add, to the very end of the upgrade procedure (after the publish
API upgrade), the following line:

ccm upgrade ccm-cms-types-mparticle --from-version 6.0.1 --to-version
6.1.0
Comment 2 Jon Orris 2004-03-29 23:59:38 UTC 
Verified.