& causing error on search

User avatar
mark
Site Admin
Posts: 5519
Joined: Tue Apr 25, 2000 6:56 pm

& causing error on search

Post by mark »

Use List/Edit urls to find the url causing the problem. It will show the title it wants to display there.

In the search url you should see &dropXSL= . Change it to (or add if not there) $dropXSL=html . Then it should work in both browsers.
dorban
Posts: 31
Joined: Fri Sep 24, 2004 12:39 pm

& causing error on search

Post by dorban »

The error is actually in the linking. I don't know where this is set though. The settings I have on my html page that makes the initial call to the search engine are...

<FORM METHOD=get name="search" ACTION="http://search.corp.firstindustrial.com/texis/search">
<INPUT TYPE="hidden" NAME="dropXSL" VALUE="html">
<INPUT TYPE="hidden" NAME="pr" VALUE="default">
<INPUT TYPE="hidden" NAME="prox" VALUE="page">
<INPUT TYPE="hidden" NAME="rorder" VALUE="500">
<INPUT TYPE="hidden" NAME="rprox" VALUE="500">
<INPUT TYPE="hidden" NAME="rdfreq" VALUE="500">
<INPUT TYPE="hidden" NAME="rwfreq" VALUE="500">
<INPUT TYPE="hidden" NAME="rlead" VALUE="500">
<INPUT TYPE="hidden" NAME="sufs" VALUE="0">

<INPUT SIZE="35" name="query" value="">
<INPUT TYPE="submit" name="submit" VALUE="Search">
</FORM>

The first page has "dropXSL=html" on the link. When I hit "next" it passes this url...

http://search.corp.firstindustrial.com/ ... SL=html%0A

If I click "2" (there are 2 pages of results) it passes...

http://search.corp.firstindustrial.com/ ... opXSL=html

And works fine. I am not sure where the "%0A" that is at the end of the first link could be coming from.

If I search for just "Security" it returns 10 pages of results. Going through using the "next" or number links pass info like the following..

Original Search http://search.corp.firstindustrial.com/ ... y=security

Page 2 - Next link (works) http://search.corp.firstindustrial.com/ ... SL=html%0A


Page 2 - #2 link http://search.corp.firstindustrial.com/ ... dropXSL=no

(Why does dropXSL get set to "no" now?)

Same until page 5...

Page 5 - Next link (broken) http://search.corp.firstindustrial.com/ ... dropXSL=no

Page 5 - #5 link

http://search.corp.firstindustrial.com/ ... dropXSL=no


Page 5 - #5 link but from original results page http://search.corp.firstindustrial.com/ ... opXSL=html


It looks to me like there are 2 issues...

1) The '%0A' getting added onto the back of pages may be causing an error (though it works in other places). Not sure where this is getting added on.

2) How do I keep dropXSL set to "html" on the templates. I don’t see a setting somewhere where I can change this.

Thanks again.
User avatar
mark
Site Admin
Posts: 5519
Joined: Tue Apr 25, 2000 6:56 pm

& causing error on search

Post by mark »

We'll have to look into it.
dorban
Posts: 31
Joined: Fri Sep 24, 2004 12:39 pm

& causing error on search

Post by dorban »

Let me know if you need any additional information from me. Thanks for your help.

Don
dorban
Posts: 31
Joined: Fri Sep 24, 2004 12:39 pm

& causing error on search

Post by dorban »

Think I have a solution... I started getting errors more and more, so I re-indexed everything with a rewalk type "New". It seems to have fixed things. I used to keep it on "Refresh" because it seemed to get me a larger collection this way. If the appliance is set for "refresh" and a document is removed from a page linking to to it, could that cause a problem?

Thanks again.
D.
User avatar
mark
Site Admin
Posts: 5519
Joined: Tue Apr 25, 2000 6:56 pm

& causing error on search

Post by mark »

I don't know how what's walked could affect the interface in the way you describe. The reason for getting more from refresh may be due to process size limit. If the new walk quits because it hits the limit you will have an incomplete walk until the next refresh. Check the walk status report to see if it quit due to process size. Adjust your process size limit to large or unlimited if you only have one walk going at a time.

I'll try to look into the xml issue today.
dorban
Posts: 31
Joined: Fri Sep 24, 2004 12:39 pm

& causing error on search

Post by dorban »

I set up the walk with "unlimited" for the process limit, and "refresh" as the type, then rewalked the site.

Not sure if this specifically causes the error, but I am getting the error again when I seach for "security". My "next" link works until I get to page six.

Page 5 link is:
http://search.corp.firstindustrial.com/ ... dropXSL=no

Page 6 link is:
http://search.corp.firstindustrial.com/ ... dropXSL=no

The error is:

The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.


--------------------------------------------------------------------------------

A semi colon character was expected. Error processing resource 'http://search.corp.firstindustrial.com/ ... ch/?query=...

<UrlDisplay>http://internal.firstindustrial.com/... ... tb_name</U
----------------------------------...

I change the dropXSL=html manually, and the error I get is now:

SAXParseException Message is: Unterminated entity reference (Unknown system ID, line 68, column 65)

Does any of that help you to diagnose where the problem is?

Thanks,
D.
User avatar
mark
Site Admin
Posts: 5519
Joined: Tue Apr 25, 2000 6:56 pm

& causing error on search

Post by mark »

Yes. It's apparently not properly escaping one of the urls on the sixth page of results. We'll have to find out why and fix. Please open a ticket so we can get the complete xml source of the problem page. Refer to this thread then we'll reply vi email so you can send it as an attachment and avoid any possible translations along the way.
tsundling
Posts: 3
Joined: Fri Jul 08, 2005 11:40 am

& causing error on search

Post by tsundling »

We are having the exact same issue and are working with support on it now. If an answer has already been found, please post it here. Thanks!
User avatar
mark
Site Admin
Posts: 5519
Joined: Tue Apr 25, 2000 6:56 pm

& causing error on search

Post by mark »

The %0A seems to have been a red herring. There was some private discussion and the problem seems to have gone away by itself in the course playing with the walk (which would have no bearing on the generated jump urls).
Post Reply