Bug 109270 - Deleting the primary language instance of a ContentBundle
Deleting the primary language instance of a ContentBundle
Status: CLOSED DUPLICATE of bug 109754
Product: Red Hat Enterprise CMS
Classification: Retired
Component: ui (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: ccm-bugs-list
Jon Orris
Depends On:
Blocks: 108447
  Show dependency treegraph
Reported: 2003-11-06 06:29 EST by Carsten Clasohm
Modified: 2007-04-18 12:59 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:59:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Carsten Clasohm 2003-11-06 06:29:30 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20030925

Description of problem:
When a content bundle has more than one language instance, the UI
shows a "delete" link on the Languages tab for all but the currently
viewed language instance. Trying to delete the bundle's primary
language instance results in a violated assertion in

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a new Article
2. Go to the Languages tab and add a language instance
3. Go to the Languages tab and click on the Delete link

Actual Results:  com.arsdigita.util.AssertionError:
equals [com.arsdigita.cms.contenttypes.Article:{id=1052}]
	at com.arsdigita.util.Assert.unequal(Assert.java:295)
	at com.arsdigita.cms.ContentBundle.removeInstance(ContentBundle.java:208)

Expected Results:  Either the Delete link should not be shown for the
primary instance, or the current language instance should be made
primary before deleting the selected language.

Additional info:
Comment 1 Richard Li 2003-12-23 13:47:57 EST

*** This bug has been marked as a duplicate of 109754 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:59:46 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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