Sakai
  1. Sakai
  2. SAK-10748

Error changing section size from limited to unlimited

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.4.0, 2.4.1
    • Fix Version/s: 2.5.0
    • Component/s: Section Info
    • Labels:
      None
    • Previous Issue Keys:

      Description

      1. Create an internally managed section with a specified size limit

      2. Edit the section

      3. Click on the radio button 'Unlimited number of students in section' and click on Update button below.

      The section does not change to unlimited, and this appears in the logs:

      WARN: Attribute 'for' of label component with id editSectionForm:sectionTable:0:_idJsp39 is not defined (2007-07-16 10:36:17,289 TP-Processor1_org.apache.myfaces.renderkit.html.HtmlLabelRenderer)

      WARN: There should always be a submitted value for an input if it is rendered, its form is submitted, and it is not disabled or read-only. Component : {Component-Path : [Class: javax.faces.component.UIViewRoot,ViewId: /editSection.jsp][Class: javax.faces.component.html.HtmlForm,Id: editSectionForm][Class: org.apache.myfaces.custom.aliasbean.AliasBean,Id: _idJsp22][Class: org.apache.myfaces.component.html.ext.HtmlDataTable,Id: sectionTable][Class: javax.faces.component.UIColumn,Id: _idJsp24][Class: javax.faces.component.html.HtmlPanelGrid,Id: _idJsp25][Class: javax.faces.component.html.HtmlPanelGroup,Id: _idJsp30][Class: org.apache.myfaces.custom.div.Div,Id: _idJsp35][Class: javax.faces.component.html.HtmlInputText,Id: maxEnrollmentInput]} (2007-07-16 10:36:19,643 TP-Processor7_org.apache.myfaces.shared_impl.renderkit.html.HtmlRendererUtils)

      The only way around this is to:

      - delete the value in the input box next to ' Limit number of students in section to'
      - click Update
      - you get a warning, viz. 'There were problems with the last action. Please see details below.'
      - click on Unlimited radio button
      - Click Update

      then the section updates correctly to unlimited.

        Activity

        Hide
        Josh Holtzman added a comment -
        Fixed -- if you can call it that -- as of r32610. It turns out that recent versions of myfaces throw away the entire form submission if the UI toggles a text input to be disabled (hence, the component's value is not sent back in the form post) via javascript. The workaround is to re-enable the text input(s) just before submission. This is stupid, but I couldn't think of another way to handle this behavior.
        Show
        Josh Holtzman added a comment - Fixed -- if you can call it that -- as of r32610. It turns out that recent versions of myfaces throw away the entire form submission if the UI toggles a text input to be disabled (hence, the component's value is not sent back in the form post) via javascript. The workaround is to re-enable the text input(s) just before submission. This is stupid, but I couldn't think of another way to handle this behavior.
        Hide
        JS added a comment -
        Verified on Sakai QA Network qa2-us (svn tags/sakai_2-5-0_QA_002) using Oracle - Built: 09/27/07 16:36 - Sakai Revision: 35908 - Server rambutan
        Show
        JS added a comment - Verified on Sakai QA Network qa2-us (svn tags/sakai_2-5-0_QA_002) using Oracle - Built: 09/27/07 16:36 - Sakai Revision: 35908 - Server rambutan

          People

          • Assignee:
            Stephen Marquard
            Reporter:
            Stephen Marquard
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: