Opensearch browser search plugin thingy tips (works for onebiglibrary.net)

I spent an unexpected amount of time during a meeting today trying to get a little search interface I wrote to properly support opensearch autodiscovery and to get the "you can install this search in firefox 2 and ie7" thingy working. Then I just did the same for this blog's opensearch interface. In case you want to do the same (get browsers to autodiscover and two-click install search plugins for your opensearch targets), here are some hints. Note, though, that they might be firefox2-specific.

  • Follow the Firefox troubleshooting tips. All of them, they all matter, it seems.
  • I might have just started from an old version, but the drupal opensearch module wasn't emitting the opensearch description element Url with text/html info as indicated as required in the troubleshooting tips.
  • The "Unable to install your search plugin thingy" error message is confoundingly unhelpful. To get useful debugging info in firefox2, go to "about:config" and enable browser.search.log (just double-click it). Then open Tools > Error Console and clear it before each time you attempt to install the search plugin. Read the output closely and go from there until the error message goes away and it works. Then you probably want to go back to about:config and disable browser.search.log again.

Here's the thing: getting opensearch-based search plugins for your browser can be a huge win for the visibility and usefulness of your resources to your user community. It's easy and it's great to have your stuff right there, an easy query away all the time. But if you want to make it easily auto-discovered, you have to get all the details exactly right *for* them.

That said, I'm not 100% certain it works in ie7. If anybody has it handy, tell me if it works for you?

Trackback URL for this post:

http://onebiglibrary.net/trackback/153

innarestin'

I recently prodded Joshua Ferraro into adding opensearch autodiscovery to his koha installation and i never actually went and added the engine. If I did I would've noticed (as you did) that it doesn't work in ff2. It turns out not all the recommendations were needed--but one...the need for a text/html Url type! Which at first seemed odd, but then made perfect sense since you get html when you use the engine. Thanks for taking the time to blog about this...

You're probably right

Come to think of it, I didn't isolate the errors to figure out which were exclusively preventing loading. Rather I just dealt with the errors in order from the error console. So the text/html thing might just be the key issue.

YMMV I guess. :)

Great post

Great post Dan, very useful info. I've passed it on to the Koha interface designer as well ...

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <pre> <code> <img> <ul> <ol> <li> <dl> <dt> <dd> <blockquote> <form> <input> <span> <object> <embed> <br>
  • Lines and paragraphs break automatically.
  • You can enable syntax highlighting of source code with the following tags: <code>, <blockcode>, <apache>, <bash>, <css>, <diff>, <dot>, <java>, <javascript>, <mysql>, <perl>, <php>, <python>, <rails>, <ruby>, <sql>, <xml>. Beside the tag style "<foo>" it is also possible to use "[foo]".

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
8 + 0 =
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.
Syndicate content

This site is Copyright (c) 2005-2008 by Daniel Chudnov. All rights reserved.

All opinions stated here are my own, and do not reflect those of my employer.