Jim Eng - 01-May-2007 12:46  Here's the relevant part of the stack trace for the IdUniquenessException: org.sakaiproject.exception.IdUniquenessException: /group/8c460c30-2339-46bd-80a6-808dac85d9c9/target2/source id=/group/8c460c30-2339-46bd-80a6-808dac85d9c9/target2/source         at org.sakaiproject.content.impl.BaseContentService.deepcopyCollection(BaseContentService.java:4667)         at org.sakaiproject.content.impl.BaseContentService.copyIntoFolder(BaseContentService.java:3950)         at org.sakaiproject.content.tool.ResourcesAction.pasteItem(ResourcesAction.java:7649)         at org.sakaiproject.content.tool.ResourcesAction.doDispatchAction(ResourcesAction.java:5939)

Jim Eng - 01-May-2007 14:12 This should be included in the QA tag 2.4.0.014. Added an error message that appears if an attempt is made to copy or move a folder into another folder that already contains an item with the same id. This was the behavior in 2.3, but the error message is not being shown in 2.4. This will fix that.

Harriet Truscott - 02-May-2007 01:00 Checked on Nightly and an error message "Could not add 1 to this folder." appears. This doesn't explain what the problem is / why they can't add the folder. Can we alter the error message to read: "You already have a folder called "1" in this folder." I will update the Help text to reflect this.

Jim Eng - 02-May-2007 05:46 I need to clarify why the message is not more specific, as Harriet suggests. This restores the message that was shown in 2.3. The circumstances under which that message is shown include (but are not limited to) the case in which a folder of the same name already exists within the containing collection. It's too late to change the logic to give different messages for other causes of this error.

Harriet Truscott - 02-May-2007 06:27 Help text will be updated to reflect this functionality.

Andrew Poland - 03-May-2007 07:13 merged to 2-4-x r29914

Harriet Truscott - 04-May-2007 07:51 verified fixed on QA1-NL