Bug 119327 - UPGRADE: No entry in cms_section_template_map for MPA
UPGRADE: No entry in cms_section_template_map for MPA
Status: CLOSED RAWHIDE
Product: Red Hat Enterprise CMS
Classification: Retired
Component: other (Show other bugs)
nightly
All Linux
medium Severity medium
: ---
: ---
Assigned To: Justin Ross
Jon Orris
:
Depends On:
Blocks: 113496
  Show dependency treegraph
 
Reported: 2004-03-29 10:35 EST by Jon Orris
Modified: 2007-04-18 13:04 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-03-29 18:59:38 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jon Orris 2004-03-29 10:35:16 EST
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 17:47:14 EST
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 18:59:38 EST
Verified.

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