History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: SAK-10093
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Venkatesh Subramanian
Votes: 3
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Sakai

Downloading Portfolios causes an Error

Created: 19-May-2007 03:02   Updated: 23-Oct-2008 08:50
Component/s: OSP: Portfolios
Affects Version/s: 2.4.0, 2.4.1
Fix Version/s: 2.5.0

Time Tracking:
Not Specified

File Attachments: 1. Text File Bug Report.txt (6 kb)
2. Zip Archive Contact Template.zip (6 kb)
3. Text File error.txt (7 kb)

Environment: Test Server: http://qa2-osp.sakaiproject.org:8084/osp-portal/

2.4.x Status: None
2.5.x Status: None
2.6.x Status: None


 Description  « Hide
Steps to reproduce the bug:

1) Create a portfolio template.
2) Create a new portfolio using this template.
3) Click the "download" button under the new created portfolio.
4) An error is generated.


P.S. The bug report has been attached.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Chris Maurer - 22-May-2007 11:29
Can you provide the template (or at least the xsl file) that was used here?

Venkatesh Subramanian - 22-May-2007 11:48
Hi Chris,

I've exported the template and attached it to this report.

Venkatesh Subramanian - 22-May-2007 11:49
Template thats causing the error

John Ellis - 17-Sep-2007 09:06
this has been fixed as a result of SAK-9219

James Sloane - 02-Jan-2008 21:32
I tested this on Nightly/SVN-Trunk and I got an unexpected error when trying to download the portfolio.
Error report attached.

Neha Saxena - 14-Mar-2008 16:38
For 2.5.x: I created a portfolio template by importing the attached file. I then tried to export this newly created portfolio and there was no error while downloading it.

Filter Maintainer - 08-Aug-2008 06:02
2.5.0 QA has been completed. Unfortunately, there were not resources available to specifically test this issue. If you find this to still be a problem in the latest release (at this point 2.5.2), please reopen the JIRA and add the latest affects version.