My problem basically has to do with the CSS popup menus in the top border. They work fine on the rest of the site, but not within the UltraSeek search engine pages (IE only). Here are the details...
We purchased the 5.1.1 version of the UltraSeek search engine about a year ago, and we recently upgraded it to version 5.3.1. I work with ASP/JScript/VBScript, JavaScript, and VBScript, and this app works with Python. Since I know nothing (and still don't) about Python, it took me a while to customize the search and result pages, but I was able to get it done.
When we uploaded the new version of UltraSeek on our new IIS 6.0 web server that runs Windows 2003, Service Pack 2, I noticed that the CSS popup menus stopped working in Internet Explorer. They work fine in other browsers, but not in IE. I think that it has something to do with the calling of a file named "iefixes.htc" within the CSS stylesheet.
You can see an example of how the CSS popup menus work properly at <!-- m --><a class="postlink" href="http://www.douglas-county.com/index.asp">http://www.douglas-county.com/index.asp</a><!-- m -->, and how they work inproperly at <!-- m --><a class="postlink" href="http://search.douglas-county.com/query.html?col=dgcoweb&qt=extension&charset=iso-8859-1">http://search.douglas-county.com/query. ... iso-8859-1</a><!-- m -->.
Can anyone see what I'm doing wrong? This is driving me nuts. Any help would be appreciated. Thanks.Looks like both are working to me...
iefixes.htc should acually fix a problem, not make one. Probably from the project IE7 (<!-- m --><a class="postlink" href="http://dean.edwards.name/IE7/">http://dean.edwards.name/IE7/</a><!-- m -->)I actually got the original soluction from <!-- m --><a class="postlink" href="http://www.ericmeyeroncss.com/">http://www.ericmeyeroncss.com/</a><!-- m -->. I had to do some customization to make it work horizontally, but it's been a great asset...especially over the old JavaScript version.
But concerning the menus, that's very strange that you could see them through both links, because I can't see the menus on the query.html page. Do you have any other suggestions? Or can anyone else try it out and let me know what they see? Thanks.
We purchased the 5.1.1 version of the UltraSeek search engine about a year ago, and we recently upgraded it to version 5.3.1. I work with ASP/JScript/VBScript, JavaScript, and VBScript, and this app works with Python. Since I know nothing (and still don't) about Python, it took me a while to customize the search and result pages, but I was able to get it done.
When we uploaded the new version of UltraSeek on our new IIS 6.0 web server that runs Windows 2003, Service Pack 2, I noticed that the CSS popup menus stopped working in Internet Explorer. They work fine in other browsers, but not in IE. I think that it has something to do with the calling of a file named "iefixes.htc" within the CSS stylesheet.
You can see an example of how the CSS popup menus work properly at <!-- m --><a class="postlink" href="http://www.douglas-county.com/index.asp">http://www.douglas-county.com/index.asp</a><!-- m -->, and how they work inproperly at <!-- m --><a class="postlink" href="http://search.douglas-county.com/query.html?col=dgcoweb&qt=extension&charset=iso-8859-1">http://search.douglas-county.com/query. ... iso-8859-1</a><!-- m -->.
Can anyone see what I'm doing wrong? This is driving me nuts. Any help would be appreciated. Thanks.Looks like both are working to me...
iefixes.htc should acually fix a problem, not make one. Probably from the project IE7 (<!-- m --><a class="postlink" href="http://dean.edwards.name/IE7/">http://dean.edwards.name/IE7/</a><!-- m -->)I actually got the original soluction from <!-- m --><a class="postlink" href="http://www.ericmeyeroncss.com/">http://www.ericmeyeroncss.com/</a><!-- m -->. I had to do some customization to make it work horizontally, but it's been a great asset...especially over the old JavaScript version.
But concerning the menus, that's very strange that you could see them through both links, because I can't see the menus on the query.html page. Do you have any other suggestions? Or can anyone else try it out and let me know what they see? Thanks.