Bug 119327 - UPGRADE: No entry in cms_section_template_map for MPA
Summary: UPGRADE: No entry in cms_section_template_map for MPA
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Enterprise CMS
Classification: Retired
Component: other
Version: nightly
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Justin Ross
QA Contact: Jon Orris
URL:
Whiteboard:
Depends On:
Blocks: 113496
TreeView+ depends on / blocked
 
Reported: 2004-03-29 15:35 UTC by Jon Orris
Modified: 2007-04-18 17:04 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-03-29 23:59:38 UTC
Embargoed:


Attachments (Terms of Use)

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.



Note You need to log in before you can comment on or make changes to this bug.