+1-888-365-2779
Try Now
More in this section

Forums / Bugs & Issues / Customised search widget added directly to page template, submit button doesn't worked in hea

Customised search widget added directly to page template, submit button doesn't worked in hea

3 posts, 0 answered
  1. Jacquie
    Jacquie avatar
    2 posts
    Registered:
    27 Jan 2015
    20 Apr 2015
    Link to this post

    I have customised the search widget which works fine when widget is dropped ​into pages, but if the code bel​ow is added directly to a page template the submit button doesn't work.

                <!-- SEARCH -->
             
                 <%@ Register TagPrefix="sitefinity" Assembly="Telerik.Sitefinity" Namespace="Telerik.Sitefinity.Web.UI" %>
        
                <fieldset id="main" class="sfsearchBox" runat="server">
         
                     <asp:TextBox ID="searchTextBox" runat="server" CssClass="sfsearchTxt" placeholder="Site search" />
                      <asp:Button  ID="searchButton" runat="server"  OnClientClick="return false;" Text="<%$Resources:SearchResources, Search %>" CssClass="sfsearchSubmit" />
        
              
                </fieldset>
            
                <!-- // SEARCH -->

  2. Atanas Valchev
    Atanas Valchev avatar
    414 posts
    Registered:
    04 Jan 2016
    23 Apr 2015
    Link to this post
    Hello,

    Try referencing the whole modified widget on the template instead of just a textbox and a button. From the information below it is hard to tell if you have the full widget functionality on the template or not.

    Regards,
    Atanas Valchev
    Telerik
     
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Sitefinity CMS Ideas&Feedback Portal and vote to affect the priority of the items
     
  3. Jacquie
    Jacquie avatar
    2 posts
    Registered:
    27 Jan 2015
    23 Apr 2015
    Link to this post

    Thanks Atanas,

    I resolved the problem by adding a placeholder to the head​er in the .master page, then added the widget to the template.

    Jacquie

3 posts, 0 answered