One more limitation from "ATLAS"?

Last post 06-22-2006 6:41 AM by mdcasanova. 5 replies.

Sort Posts:

  • One more limitation from "ATLAS"?

    06-21-2006, 10:07 AM
    • Member
      420 point Member
    • Kerkhoff
    • Member since 01-17-2005, 5:21 PM
    • Posts 84
    Hi, I have this simple scenario...

    One ModalPopup extender with an UserControl inside (placed in design time)..
    this UserControl has a TextBox, a ImageButton and a CheckBoxList, all inside an UpdatePanel.

    My problem is, the imagebutton doesn't fire the click event :(...even if it is outside of UpdatePanel...

    Without this and another features, ATLAS is a greate limiter of code organization...
    I want to place my page fragments inside usercontrols to not copy/replace code and I can't :(...
    the same with UpdatePanel loaded after Page_Init...but this...I forgive "ATLAS" for while...

    Any suggestion? Thanx...
  • Re: One more limitation from "ATLAS"?

    06-21-2006, 1:16 PM
    • Member
      30 point Member
    • puznee
    • Member since 06-20-2006, 7:47 PM
    • Posts 20
    Kerkhoff,
    Your problem is probably because items in the user control are being renamed by asp.net to avoid naming collisions. Say your ImageButton has id="btn1". The actual id tag, when rendered, will look something like "usercontrol1_btn1". If you view-source on the page, you should be able to verify whether or not your button is actually rendering with the id you think it is.

    Try setting the Modal Popup TargetControlID programatically using btn1.ClientID instead.

    Gabe
  • Re: One more limitation from "ATLAS"?

    06-21-2006, 2:18 PM
    • Member
      420 point Member
    • Kerkhoff
    • Member since 01-17-2005, 5:21 PM
    • Posts 84
    Thanx for ur help..
    but unfortunely my problem isn't that :(

    my target control works fine..

    any other suggestion?

    thanx :)
  • Re: One more limitation from "ATLAS"?

    06-21-2006, 4:16 PM
    • Member
      30 point Member
    • puznee
    • Member since 06-20-2006, 7:47 PM
    • Posts 20
    Oops! I misread your post. Sorry about that :-)

    You say the imagebutton doesn't fire the click event... Do you mean a client-side click event, or a postback?

    If you mean a client-side event, I have no idea what's wrong. If you mean a postback, this is what worked for me (using regular button controls):

    1) Make sure you are using the latest snapshot of the source from CodePlex
    2) Add "UseSubmitBehavior=false" to your control (this attribute is part of the button control... but I didn't check to see if it exists in the ImageButton control)

    I'm not using the update panel, however, because I couldn't get them to work with the postbacks.
  • Re: One more limitation from "ATLAS"?

    06-21-2006, 5:07 PM
    • Member
      420 point Member
    • Kerkhoff
    • Member since 01-17-2005, 5:21 PM
    • Posts 84
    I mean the postback event
    yes...this is my problem :(
    I already tryied with UseSubmitBehavior (that's not present in ImageButton) to false...but I have a UpdatePanel and this doesn't work with PostBacks :(

    And without UpdatePanel my popup doesn't make sense..

    Any suggestion? thanx!
  • Re: One more limitation from "ATLAS"?

    06-22-2006, 6:41 AM
    • Member
      260 point Member
    • mdcasanova
    • Member since 02-13-2004, 1:33 AM
    • Posts 59

    I am having exactly the same problem as well, hence i've decided to tag along with this post, as opposed to creating a new thread.

    I am trying to impliment a Sign-In functionality with the ModalPopupExtender. Is there a way to provide user feedback within the Modal Popup itself if the authentication process was unsuccessfull, or otherwise, set the forms authentication cookie and sign the user in when the popup has been dismissed?

Page 1 of 1 (6 items)