Thanks to DNN ver 4.8.x automatically wrapping a module's Settings.ascx control with an AJAX update panel whenever AJAX is enabled by the host, I had another previously published module break after the user upgraded the framework to DNN 4.8.2.  In order for the >, <, >>, and << link buttons of the core DualListControl to move list items between the available and assigned lists, full postbacks are currently required.  Until this can be taken care of with core changes, the following work around can be used in the Page_Load of Settings.ascx when a dual list control is used:

If Framework.AJAX.IsEnabled Then
    For Each ctrl As Control In dlcAuthorizedContacts.Controls
         If Not ctrl.ID Is Nothing AndAlso ctrl.ID.StartsWith("cmd") Then
            Framework.AJAX.RegisterPostBackControl(ctrl)
         End If
    Next
End If

In the above, dlcAuthorizedContacts is a reference to my DualListControl. This problem is similar to the problems experienced with use of the rich text editor (FCKEditor) control in Settings.ascx. It appears that many of the core user and web controls will need to be modified to register buttons, link buttons, and image buttons (etc.) as PostBackControls so that the controls can be used within AJAX update panels.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner