Hyperlink NavigateUrl="#" causing HTTP error

3 posts, 0 answers
  1. Oliver
    Oliver avatar
    14 posts
    Member since:
    Nov 2007

    Posted 21 Feb 2008 Link to this post

    Hi,

    I have a user control which has:

    <asp:HyperLink ID="lnkDelete" runat="Server" NavigateUrl="#" Text="Delete" />

    and I have the Tool Tip control referencing lnkDelete.  (So I can't use an HTML <a> tag).

    Now this behaviour works in an aspx page, but as soon as it runs within a control it fails, as the hyplink control is being rendered with an href to the path of the user control.  So I end up getting a HTTP 403 error.

    Is there any way of overriding this default behaviour of the hyperlink within a control?  This must be common....

    Thanks!

  2. Oliver
    Oliver avatar
    14 posts
    Member since:
    Nov 2007

    Posted 22 Feb 2008 Link to this post

    Me again,

    I also tried using a <a ID="lnkDelete" runat="server" NavigateUrl="#"/>
    but that did the same.

    I also created a label and gave it a style to look like a link, but the tool tip event wasn't raised on the onclick of a label (perhaps obvious in hindsight).

    Hope someone can advise.

  3. Tervel
    Admin
    Tervel avatar
    1337 posts

    Posted 25 Feb 2008 Link to this post

    Hi Oliver,

    We are not sure how exactly the tooltip is related to your configuration and to your problem.
    Some useful information - in the coming Prometheus update to be released by tomorrow we have made several modifications to the tooltip and now it is able to bind better in some scenarios (by better we mean automatically - without the need for the developer to write any code-behind). One such improvement is when the tooltip an its user control are in a UserControl.

    Our suggestion is to get the SP2 update once it is out (today or tomorrow), and give it a try. If it does not fix your scenario, then it is best to open a support ticket and send us a sample project that demonstrates the issue as we are not sure from the description where the problem is.


    Greetings,
    Tervel
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
Back to Top