Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Search problem in 4.5.3Search problem in 4.5.3
Previous
 
Next
New Post
5/31/2007 7:36 AM
 

Hi all,

I've just upgraded my local dev version of DNN to 4.5.3, and the first thing i noticed is the 'web' and 'site' radio button options alongside the search textbox.  This was very noticible because it threw my site (skin) out a bit because i had a very limited area to squeeze the search box into, and the addition of these options meant it didn't fit nicely anymore. 

So.... i thought there must be somewhere to turn off the options and let the search feature default back to legacy mode (i.e. site search only), but to my surprise I couldn't find anywhere to set these search options, and 'hide' the 'web' / 'site' radio buttons. 

Furthermore, the web search doesn't even work... well not in Firefox 2.0 anyway (maybe it's trying to pop up a new window?) - confirmed, just tested in IE and had to set the pop up blocker to allow the web search to work.

My question is, can anyone tell me how to disable these new search options?  Even if i have to hard code it.  I've look in the following locations with no luck:

/admin/search/InputSettings.ascx
/admin/search/SearchInput.ascx

any help would be appreciated.

Thanks,

Tim

 


Tim NetPotential www.netpotential.co.nz
 
New Post
5/31/2007 9:13 AM
 

Look at this blog post by Sebastian:

I have also quoted a posting by Shaun without the extraneous conversation

sbwalker wrote

I am a bit embarrassed about this... I added the new search options but they were supposed to be disabled by default...

The new options for Web and Site were added so that it is simple for users to include the standard "search the web" or "search my site" functionality which is available on many websites. It was implemented in a way which is completely extensible:

1. To enable/disable the options in the skin object, you simply set the public attributes in your skin ( like any other skin object ):

<dnn:SEARCH runat="server" id="dnnSEARCH" showWeb="False" showSite="False" />

or for HTML skins, in the skin file:

  <Object>
    <Token>[SEARCH]</Token>
    <Settings>
      <Setting>
        <Name>showWeb</Name>
        <Value>False</Value>
      </Setting>
      <Setting>
        <Name>ShowSite</Name>
        <Value>False</Value>
      </Setting>
    </Settings>
  </Object>

Note that you can set one option to True and the Other to False for even more customization. In addition there is another attribute:

UseWebForSite="True"

This option can be used if you want to leverage a search engine like Google for your internal site search - rather than using the native DNN search engine. In this case the results for a Site search will return publicly accessible results for only your website from a remote search engine.

2. You could also set them in the source code as per John's suggestion above - however since this is core code it means that your change may get overwritten on the next upgrade.

3. If you actually want the Site and Web options in your site, you also have the ability to configure them even more in the related RESX file ( Search.ascx.resx ) which is accessible using the DNN Language Editor:

    <data name="URL.Text">
        <value>http://www.google.com/custom?hl=en&amp;client=pub-9770992166002654&amp;sitesearch=[DOMAIN]&amp;q=[TEXT]</value>
    </data>

In this case the Web search is done using Google and it is passing an affiliate ClientID, optional SiteSearch domain name, and the search query. Any or all of the values in this resouce string can be modified to suit your needs. Note that by default, the DotNetNuke project ClientID is included in the search query, as it is an inobtrusive way for us to generate a bit advertising revenue to help offset the costs of provifing community programs and managing the open source project.

You can even support other search engines simply... for example for MSN you could specify:

    <data name="URL.Text">
        <value>http://search.msn.com/results.aspx?q=[TEXT]</value>
    </data>

This enhancement was inspired by Steve Orr's recent article on Gadgets in AspNetPro magazine.


Joe Brinkman
DNN Corp.
 
New Post
5/31/2007 11:13 AM
 

please note, that Shaun's solution 3 has the same limitiation as 2, as it will get overwritten on updates.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
5/31/2007 12:00 PM
 

Good point Sebastian.

This really needs to be an admin setting.


DotNetNuke Modules from Snapsis.com
 
New Post
5/31/2007 12:13 PM
 

I agree, John. Would you be so kind and add the feature request into gemini please? Thank you.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Search problem in 4.5.3Search problem in 4.5.3


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out