Hi Jim,
Yes, on reflection (and review of the documentation) I seem to have made an incorrect assumption; that as ht://Dig is able to use URLs for certain parameters (e.g. start_url) that it would be able to use URLs for all parameters. It's a shame that it doesn't.
I wonder if you might have any pointers for my situation; in our application, the 'wrapper' is an HTML page that's content is dynamically rendered when it's URL is called, and in which the appropriate content (such as links, images, styling etc.. which can change over time) is placed.
In order to retain the dynamism I need to be able call the standard wrapper URL into which I insert the results of the search (by placing the marker in the appropriate position); the only apparent alternative is to create a static wrapper page which resides in the common directory, but then that needs updating as the design of the site changes, something that I was hoping to avoid as it defeats the 'change once, apply everywhere' principle.
Is there perhaps a way that we can call the htsearch program to return a stream rather than an HTML page, which can then be manipulated and placed in the required position?
Any thoughts gratefully received!
Best Regards
Jon
From: Jim <[EMAIL PROTECTED]> To: Jon Sumpster <[EMAIL PROTECTED]> CC: [email protected] Subject: Re: [htdig] Wrapper configuration Date: Sat, 19 Mar 2005 02:04:43 -0700 (MST)
On Thu, 10 Mar 2005, Jon Sumpster wrote:
I seem to be having trouble getting the wrapper functionality to work when using a URL to specify the wrapper page on a remote server. If I have the wrapper.html page in the 'common' directory it works fine, but unfortunately I'm working in an environment where the owner/author of the wrapper is remote and should not have access to this directory. The intention is for them to modify the wrapper whenever they like; all they should do is include the $(HTSEARCH_RESULTS) etc.. in the appropriate places.
In my test environment, in the htdig.conf file I am specifying the following:
search_results_wrapper: http://192.168.20.18/development/searchwrapper.html
To the best of my knowledge this has never been supported. The template files are expected to be regular files accessible through a mounted file system.
What happens is that this line is ignored, and the default 'header.html' and 'footer.html' (both in the 'common' directory are used instead). If I specify the following in the htdig.conf file:
The line is not really ignored. It is read and htsearch attempts to open the file. However no file by the specified name is accessible through the file system so htsearch falls back to using the local header/footer.
The documentation indicates that a url-based syntax should be fine to fetch the required html file but I can't seem to get it to work at all - does anyone have any ideas please?
Where does the documentation indicate this? An update is probably in order if it is implying that template files can be retrieved via URL's.
Jim
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ ht://Dig general mailing list: <[email protected]> ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-general
