[Building Sakai] Bug: 2+ Custom Parameters Separated by New Lines Broken after Saving sakai.basiclti Tool

[Neal Caidin]

Hi Raymond,

If you have a Jira account, you can create a new bug report in it. It is open to the community.

Cheers,

Neal Caidin

Sakai CLE Community Coordinator
nealcaidin at sakaifoundation.org
Skype: nealkdin
AIM: ncaidin at aol.com



On Jun 2, 2013, at 1:30 PM, Raymond Naseef <raymond.naseef at gmail.com> wrote:

> Hi All,
> 
> I found a bug to report, and am not sure if I have rights to enter Jira into Sakai CLE.  Here is the bug:
> 
> 
> Title:
> 2+ Custom Parameters Separated by New Lines Broken after Saving sakai.basiclti Tool
> 
> 
> Description:
> Custom Parameters may be edited in TextArea, separated by new lines.  If this is done, and the tool is edited from the Site Editor, the field is a text field, instead of TextArea, and the custom parameters become one entry containing "<br/>".
> 
> 
> Steps to reproduce:
> This takes two steps to produce:
>     [a] Save custom parameters
>     [b] Edit the tool as admin
> 
> [a] Save custom parameters
> a1. Login as user that has the ability to modify the sakai.basiclti properties
> a2. Open the page showing the sakai.basiclti tool
> a3. Click on the tool's edit icon (looks like paper with pencil on my computer)
> a4. In "Custom Launch Parameters", enter multiple parameters one-per-line
> a5. Press button "Update Options" to save the changes
> 
> [b] Edit the tool as admin
> b1. Login as admin
> b2. Click "Sites" to open list of sites
> b3. Click on ID of site with the sakai.basiclti tool
> b4. Click on button "Pages"
> b5. Click on ID of page containing the sakai.basiclti tool
> b6. Click on button "Tools"
> b7. Click on ID of the sakai.basiclti tool
> * Take a look at imsti.custom field - notice this is text field with multiple entries including "<br/>"
> b8. Press "Save" button
> 
> 
> Workaround/Solution:
> Entering multiple parameters separated by semicolon appears to work fine.  Allowing multi-line entries would require using TextArea in Site Editor, or "cleaning up" the entry by replacing "<br/>" with semicolons.  Using semicolons will "mess up" the view in the TextArea; one workaround for that is to replace semicolons with "<br/>".
> 
> My preference would be to either:
> [A] Do not have two different forms for editing these parameters
> AND/OR
> [B] Use one set of input for each parameter instead of TextArea.  Coding this is a little challenging, but not so hard to do.  Add new input fields when the user asks for them, and hide elements when the user asks to delete one.  Some field needs to be sent to the user indicating parameters to delete.  This makes a nice interface.
> 
> 
> 
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130602/63c840c0/attachment.html