Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
running QuickSearch from a custom page
B_Looser
Greetings,
Is there a quick and easy way to apply the QuickSearch functionality to a text box and button on one of our custom pages?
Apparently, we will want to put QuickSearch in an iframe on the custom page, since that is how it is called onto the main_display.asp (through an iframe).
So, once we have QuickSearch showing on our custom page, through an iframe, and the user enters an item, how can we direct the code, so that the results will show on the main page, like it does when we run it from the main page?
Thank you,
Jim
Find more posts tagged with
Comments
B_Looser
It was mentioned to me in the other forum, that the QuickSearch has a GUID associated with it, and that somehow that would fit into the solution.
However, I tried to find this GUID in the database, and I cannot find it. I'm wondering how I can find that GUID, and then how I can apply it to get what we need (the results showing on the main page) once we have it?
Jim
msrinivas
In include/Constants.asp page of your web client code refer to the value of c_FullTextIndexGUID.
It is {F24FC776-00D2-4ED7-ADA3-9D5288B149A3}.
HTH
B_Looser
OK, thanks for the information and for being happy to help.
Next question, where does the "quicksearch.asp" page open the "find.asp" page? Seems that is where we would want to shoot to the main.asp page from.
That is really the crux of the question: How can we display QuickSearch on a custom page, and have the results shoot out to the main page?
Jim
msrinivas
In the SDK examples available on support site there is a Search.asp example. You can use that as your starting point and use the quick search GUID that I provided you to accomplish the same.
Migrateduser
Also, you do not have to run QuickSearch from an IFrame. As you've probably noticed, the main page of the web client is very complex, with a mass of nested tables and multiple IFrames. I was unable to get the UI to work exactly right on all platforms and browsers (and different browser versions)... without using the IFrame. I believe there were issues getting the text box to resize properly.
Therefore, if I were you, I would not use an IFrame where it isn't really required.