I think it might be as simple as placing a form on your masterpage and then set the post action to the result page you want. Don't know if you need to pass some parameter to it though :-)
I cannot go down that route due to the form within a form problem. The other way to accomplish what you have suggested would be to place the code in a user control, place that in the master page and have the user control redirect to another page and take the querystring as the search parameter.
The way in which the Google search control works (with javascript etc) would be a real pain. I have also noted that Google have deprecated the old search API and is now asking people to use the newer version. For that reason I dont really think that this is a viable option.
I'm looking at Examine and Lucene currently as that looks to be a lot more flexible, it would also solve another problem I have of pulling in data from a third party app (which is why I'm moving away from the basic XSLTSearch in the first place)
Hi Greyhound, yeah this search control won't necessarliy do what you need. A better bet for multi-page search results is definitely Examine. I suppose to could also use Google Site Search to popup a new div with the search results rendering them in a new windows look-a-like, but for search srobustnesss, indexing, and freshness, I think a local Examine implementation is your best bet.
Well... I've spent a couple of days looking at Lucene and Examine and I'm pretty well confused now.
I've looked at the FarmCode example of a custom data source and I'm almost there with that concept. The only problem is getting this to work with umbraco and I cannot see any examples of code where the Umbraco admin and site search is working along side a custom data source index (ie. I would like users to be able to click search on my website and get results returned from (a) Umbraco CMS content (b) The blog posts created in BlogEngine.Net.
The other issue I seem to be having is that the Back Office search wont work when I update my web.config file with the settings in the examples.
Existing original web.config (Backoffice search works ok)
Can anyone point me in the direction of some examples of scenarios where the existing Umbraco Examine is fully functioning and a custom index/search is implemented along side of this? And as its Christmas, it would be a bonus if there were also an example of some code that pulls in the results from both index sets (Umbraco CMS and custom data source)!!
You shouldn't be updating the existing web.config settings, you'd need to update examineSettings.config to include your own implementation of searching and indexing your custom data. See this blog post (includes sample project) for more info.
So they are definitely different. The Examine.LuceneEngine line above stops Umbraco building the index and it breaks the BackOffice search facility from within Umbraco itself. I'm looking for a way to keep the BO seach functionality and be able to create new indexes.
The differences above are really stumping me as I can find absolutely no information on creating a custom index and keeping existing Umbraco functionality.
i am new user of umbraco, so i can not understand search control. can anybody teach how to search content on textbox enter event and show result in search.aspx page.
Create search results in a new page
Hi,
Has anyone implemented this control on a new page. For example:
1. Have a fixed search box at the top of each page
2. When the user clicks on search they are redirected to a new page and the results are listed out.
I have achieved this with the xslt search but cant seem to "work out" how to achieve it with the Google search.
Thanks.
Hi Greyhound
I think it might be as simple as placing a form on your masterpage and then set the post action to the result page you want. Don't know if you need to pass some parameter to it though :-)
/Jan
Hi Jan,
I cannot go down that route due to the form within a form problem. The other way to accomplish what you have suggested would be to place the code in a user control, place that in the master page and have the user control redirect to another page and take the querystring as the search parameter.
The way in which the Google search control works (with javascript etc) would be a real pain. I have also noted that Google have deprecated the old search API and is now asking people to use the newer version. For that reason I dont really think that this is a viable option.
I'm looking at Examine and Lucene currently as that looks to be a lot more flexible, it would also solve another problem I have of pulling in data from a third party app (which is why I'm moving away from the basic XSLTSearch in the first place)
Thanks for taking the time to reply.
Hi Greyhound, yeah this search control won't necessarliy do what you need. A better bet for multi-page search results is definitely Examine. I suppose to could also use Google Site Search to popup a new div with the search results rendering them in a new windows look-a-like, but for search srobustnesss, indexing, and freshness, I think a local Examine implementation is your best bet.
Good luck!
Thanks,
Nik
Well... I've spent a couple of days looking at Lucene and Examine and I'm pretty well confused now.
I've looked at the FarmCode example of a custom data source and I'm almost there with that concept. The only problem is getting this to work with umbraco and I cannot see any examples of code where the Umbraco admin and site search is working along side a custom data source index (ie. I would like users to be able to click search on my website and get results returned from (a) Umbraco CMS content (b) The blog posts created in BlogEngine.Net.
The other issue I seem to be having is that the Back Office search wont work when I update my web.config file with the settings in the examples.
Existing original web.config (Backoffice search works ok)
Example code web.config (Indexes not created on publishing page and BackOffice search not working)
Can anyone point me in the direction of some examples of scenarios where the existing Umbraco Examine is fully functioning and a custom index/search is implemented along side of this? And as its Christmas, it would be a bonus if there were also an example of some code that pulls in the results from both index sets (Umbraco CMS and custom data source)!!
Thanks.
You shouldn't be updating the existing web.config settings, you'd need to update examineSettings.config to include your own implementation of searching and indexing your custom data. See this blog post (includes sample project) for more info.
Cheers,
/Dirk
Hi Dirk,
Thanks for getting back to me.
The original line in the Umbraco 4.5 installation:
The line in the example post which I have been using:
So they are definitely different. The Examine.LuceneEngine line above stops Umbraco building the index and it breaks the BackOffice search facility from within Umbraco itself. I'm looking for a way to keep the BO seach functionality and be able to create new indexes.
The differences above are really stumping me as I can find absolutely no information on creating a custom index and keeping existing Umbraco functionality.
Ta.
hi everbody,
i am new user of umbraco, so i can not understand search control. can anybody teach how to search content on textbox enter event and show result in search.aspx page.
Please Guys reply as soon as possible.
Thanks & Regards,
Manish
is working on a reply...