Bug 88302 - Upgrade Scripts for troika cms multilingual items
Upgrade Scripts for troika cms multilingual items
Status: CLOSED RAWHIDE
Product: Red Hat Enterprise CMS
Classification: Retired
Component: other (Show other bugs)
nightly
All Linux
medium Severity medium
: ---
: ---
Assigned To: ccm-bugs-list
Jon Orris
:
Depends On:
Blocks: 97511
  Show dependency treegraph
 
Reported: 2003-04-08 14:27 EDT by Bryan Che
Modified: 2007-04-18 12:52 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-08-22 08:50:21 EDT
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 Bryan Che 2003-04-08 14:27:25 EDT
Archiving info here so we remember it.

> > e) During the training week, I was trying to use the pset code with a > test
5.3 build.  5.3 had some issues - no preview link, item templates > tab doesn't
work, no way to add a non-UDCT to a section - which I'm > assuming will be fixed
or explained.  However, I discovered one > disturbing thing; the pset code
compiles with 5.3, but if you try to > create a Story content item (the content
item used in the pset), you > get an error.  I traced this down to the fact that
every content item, > including assets, now needs to define a content bundle,
and it's not > immediately obvious how to do this (I know it's done in >
PageCreate.java, but I had problems getting text assets to define a >
ContentBundle).


ML will require a nontrivial upgrade script that invents a bundle in
between existing items and their parent folder.

Whether a bundle is required as the parent of an item or not is largely
determined by the ItemResolver (MultilingualItemResolver). For DP we use
a subclass of the CMS MultilingualItemResolver that treats assets
specially and allows for assets that are not in bundles, but directly in
folders.

David

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