Bug 111549 - Deletion of ContentBundle with live versions
Summary: Deletion of ContentBundle with live versions
Alias: None
Product: Red Hat Enterprise CMS
Classification: Retired
Component: ui
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: ccm-bugs-list
QA Contact: Jon Orris
Depends On:
TreeView+ depends on / blocked
Reported: 2003-12-05 08:26 UTC by Carsten Clasohm
Modified: 2007-04-18 16:59 UTC (History)
0 users

Clone Of:
Last Closed: 2006-07-12 09:06:59 UTC

Attachments (Terms of Use)

Description Carsten Clasohm 2003-12-05 08:26:02 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20030925

Description of problem:
When a ContentBundle has more than one language instance and one of
the non-primary instances has a live version, the Browse tab under
Content Center -> Content Section shows a "delete" link for the
bundle. Clicking this link removes the bundle and all draft versions,
but leaves behind the live version in the database. Afterwards, there
is no way to reach this live version via the UI.

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

How reproducible:

Steps to Reproduce:
1. Create a new Article
2. Add a new language instance
3. Publish this language instance
4. Go to Content Center -> Content Section -> Browse
5. Delete the Article
6. Take a look at the cms_items table and see that the live version of
the second language instance still exists


Expected Results:  The "delete" link should not be shown if any of the
bundle's language instances have a live version.

Additional info:

Comment 1 Richard Li 2003-12-05 11:56:55 UTC
carsten, is this the same as bug 111505?

Comment 2 Carsten Clasohm 2003-12-05 17:44:21 UTC
No, although both are similar. This bug is about the delete link on
the Browse tab of the Content Section, where bundles are listed. Bug
111505 is about the Languages tab of a single content item, where
language instances are listed.

Comment 3 Carsten Clasohm 2006-07-12 09:06:59 UTC
Closing old tickets.

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