Tuesday, March 6, 2012

Super LOV Release 2.0.1

I've just release Super LOV 2.0.1 into the wild. This patch release offers very little in terms of new features but fixes a number of bugs and even patches a XSS vulnerability so I recommend everyone using Super LOV to upgrade ASAP.

The new version can be downloaded from our plug-in downloads page here:
http://skillbuilders.com/plugins

Also, although it's not noted anywhere, I've applied the XSS vulnerability patch to the download file for Super LOV version 1.3 for those of you that have not yet upgraded to APEX 4.1.

Here's a summary of the updates:


  • Fixed bug where mapped values were being inadvertently escaped (thanks to Deepthi Bommera for identifying the issue)
  • Fixed bug where LOV would not load if APEX was run in languages other than English (thanks to Dennis Verdaasdonk and Yuri Arts for identifying the issue and to Patrick Wolf for helping me see the error of my ways)
  • Fixed bug that prevented keyboard actions from working when report regions existed on the page (thanks to Dennis Verdaasdonk for identifying the issue)
  • Fixed but that prevented modal dialog from opening in IE when browser was in quirks mode (thanks to Martin D’Souza for identifying the issue and providing a solution)
  • Added support for native Dynamic Actions including Set Value, Get Value, Hide, Show, Enable, and Disable (thanks to Martin D’Souza for the suggestion)
  • Renamed fieldset id to work with $x_ItemRow  (thanks to Martin D’Souza for the suggestion)
  • Fixed bug where change event fired when twice when in enterable mode. Now native change event is suppressed and a change event is triggered when a change is made according to standard use of the plug-in (thanks to Martin D’Souza for identifying the issue) 
  • Set input value to be escaped while rendering input to prevent XSS vulnerabilities (thanks to Patrick Wolf for identifying this issue)
  • Fixed bug that generated checksum error when readonly items were on the page (thanks to Paul for identifying the issue and to Patrick Wolf for providing a solution)


10 comments:

  1. Dan, thanks again for the release.
    A new bug seems to have found his way into 2.0.1:
    When using the mode "Enterable - Restricted to LOV" with 2.0.0 hitting Enter once was enough to display the LOV in IE8. With 2.0.1 you have to hit enter two times for the LOV to open in IE8.

    I have two applications on apex.oracle.com to illustrate the issue.

    workspace: crmapextest
    user: test
    pwd: test

    application 27147 uses 2.0.0
    application 41133 uses 2.0.1

    BR Paul

    ReplyDelete
  2. Paul,

    Thanks for letting me know. I've modified the plug-in to use keypress over keydown and it seems work with all browsers/versions now.

    I've released this as Super LOV 2.0.2 and it can now be downloaded from out site.

    Regards,
    Dan

    ReplyDelete
  3. Dan,

    Can you please explain the solution Patrick provided to you guys for the generated checksum error. I'm fighting with this when trying to submit from a jquery fancybox and I think it must be similar to the problem you had.

    Thanks a lot,

    Mark

    ReplyDelete
  4. Mark,

    All we did was move the call to get the APEX item name to the inside of an if block that made sure the item was being rendered. Not sure if that really helps you.

    May be easier to help if you set up an example on apex.oracle.com and provide developer credentials.

    Regards,
    Dan

    ReplyDelete
  5. Please let me know how to remove the clear button as i dont want to display it to my users.

    ReplyDelete
  6. Anonymous,

    You should be able to use CSS. Try adding the following to your page header between style tags:

    button.superlov-modal-delete {
    display: none;
    }



    Regards,
    Dan

    ReplyDelete
  7. In the super lov, there is an extra column that displays the APX$ROWNUM. My users dont want this column to be seen. Please let me know how to hide it.

    Thanks,
    DS

    ReplyDelete
  8. Hi DS,

    This is a bug that occurs in APEX 4.2. I will fix this in the next release of the plug-in. The workaround for now is to utilize the Hidden Columns setting to hide that column. Just take the number of columns you have in your LOV and add 1. Take that number and place it in the hidden columns setting and the column will now show.

    Regards,
    Dan

    ReplyDelete
  9. Hi Dan,

    Thanks for your reply. I hope you will release the plugin soon else it is going to be a tough task changing the plugin setting in all the pages to hide the extra apex column. But I have another issue. When I make the return field as hidden, both the scrollbars appear. It happens only when I make the field hidden else it appears normal. Can you help?

    Thanks,
    DS

    ReplyDelete
  10. DS,

    Please email me directly.

    Regards,
    Dan

    ReplyDelete