RSS feed not validating

[MichaelECMD]

Hello!,

I'm having trouble adding my search engine to the Opensearch website:
http://a9.com/-/opensearch/

When i try to add my search engine it says the description file is OK (which it is) but when i try a sample search query i get an error message saying the OpenSearch feed is invalid..

puzzled i tried to validate the feed which unfortunately doesnt pass validation
http://feedvalidator.org/check.cgi?url=http%3A%2F%2Fwww.klinksolutions.com% 2Fcgi-bin%2Fsearch%2Fsearch.cgi

this is the CGI file directly created by the Zoom Search software..am i doing something wrong or does the software actually create non working scripts?

im guessing that the 'greater then' sign ( after w3.org/2005/Atom"> ) shouldn't be there.. but since the CGI files seem encrypted i cannot resolve this error:

<rss version="2.0" xmlnspensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"> xmlns:zoom="http://www.wrensoft.com/zoom/response/5.0/schema/">

any ideas on how to fix this error?

thanks in advance!

[Ray]

You're right, this is a bug in the current build (V5.1 build 1009) of the CGI. The greater than sign should not be there. We will fix this in a patch release, which should be available sometime this week.

Note that the CGI files are not "encrypted". They are compiled binary executables, coded in C++ for performance reasons. See this FAQ:
http://www.wrensoft.com/zoom/support/platforms.html#cgi

[MichaelECMD]

Thank you for your response! I am looking forward to the patch release!

in the meanwhile , is there any way i can manually configure the .CGI file to work ? since opening them in a simple text editor does not work,

or is it impossible to decompile these files ?

[David]

It is possible to patch, hack & reverse engineer a binary executable, but you really need to be an expert programmer to do this. If you needed to ask the question, then you don't have the experience required to patch the binary file. Sorry.

But we'll have a new version out in a couple of days with a bug fix.

Another solution would be to fall back to an older V5 build that didn't have this particular bug. But older versions don't comply with the newer OpenSearch specifications (they just changed the spec's in the last few months).

[MichaelECMD]

thanks for all the replies so far!

one last question..if i was to purchase a paid version of the software now,

will i be able to install the patch without having to pay an extra fee of some sort..or will it be a 'free upgrade / free bugfix' ?

[David]

The bug fix will be in release V5.1 build 1010. This will be a free upgrade to anyone who has purchased any V5.x release.