Bug 113745 - Deletion of Home Folder gives 'unexpected error'
Summary: Deletion of Home Folder gives 'unexpected error'
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise CMS
Classification: Retired
Component: APLAWS-usability
Version: nightly
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: ccm-bugs-list
QA Contact: Daniel Berrangé
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-01-16 23:46 UTC by Lindsay Ould
Modified: 2008-01-03 20:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-01-03 20:05:35 UTC
Embargoed:


Attachments (Terms of Use)
Error report for Bug 113745 (49.50 KB, application/msword)
2004-01-16 23:48 UTC, Lindsay Ould
no flags Details

Description Lindsay Ould 2004-01-16 23:46:20 UTC
Description of problem:created folder named 'removal' - selected it 
as home folder and then tried to delete folder - got unexpected error


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


How reproducible: always


Steps to Reproduce:
1.logon as admin
create new folder 'removal'
2.assign as home folder
3.log out
4.log in (admin)
5.select parent folder to 'removal'  
6.select delete link for 'removal'
Actual results:
unexpected error - 

Expected results:


Additional info:

Comment 1 Lindsay Ould 2004-01-16 23:48:35 UTC
Created attachment 97068 [details]
Error report for Bug 113745

Comment 2 Scott Seago 2004-01-17 00:05:43 UTC
The actual bug you're seeing has already been resolved which related
to either clicking delete or clicking the item title in the folder list.

However, with that fix there's still currently a problem. Actually,
I'm failing to delete any content item, not just folders.
This may be a recently-introduced bug on the tip. We'll need to
confirm first that item deletion works on the tip. a partial stack
trace I'm getting w/ item deletion:

com.redhat.persistence.engine.rdbms.RDBMSEngine$4: ORA-01407: cannot
update ("CI"."CMS_ITEMS"."ITEM_ID") to NULL

	at
com.redhat.persistence.engine.rdbms.RDBMSEngine.execute(RDBMSEngine.java(Compiled
Code))
	at
com.redhat.persistence.engine.rdbms.RDBMSEngine.flush(RDBMSEngine.java(Compiled
Code))
	at
com.redhat.persistence.engine.rdbms.RDBMSEngine.flush(RDBMSEngine.java(Compiled
Code))
	at com.redhat.persistence.Session.flushInternal(Session.java(Compiled
Code))
	at com.redhat.persistence.Session.flush(Session.java(Compiled Code))
	at
com.arsdigita.persistence.DataObjectImpl.delete(DataObjectImpl.java:380)
	at com.arsdigita.domain.DomainObject.delete(DomainObject.java:324)
	at
com.arsdigita.cms.ui.folder.FolderBrowser$ItemDeleter.cellSelected(FolderBrowser.java:463)

Rafi, this may be a persistence issue. Why is item.delete() trying to
set the primary key to null instead of removing the row?


Comment 3 Scott Seago 2004-01-17 00:06:22 UTC
Randy, could this be related to your audit trail edits?

Comment 4 Scott Seago 2004-01-17 20:27:37 UTC
This is now fixed on the staging server, checked into the aplaws-w3
branch, to be integrated on dev next week.

Comment 5 David Lawrence 2006-07-18 03:13:07 UTC
QA_READY has been deprecated in favor of ON_QA. Please use ON_QA in the future.
Moving to ON_QA.


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