Radio.active

I installed the pLessFix script a while back, so my question is do I need to remove that fix now, and if so how? Tools are so much friendlier to non-Geeks like me.

I was never quite sure whether Andy Fragen's pLessFix script was working or not, since I didn't know how to do iterative testing with a script. Now I should be able to install/uninstall easily and see the effect.

pLessFix Tool. I think I've successfully converted my pLessFix into a tool. I have to let it burn in for a couple of days to make sure it's working like I think it's supposed to.
For this tool the advantage is easier installation and constant updating in case UserLand changes the drivers. If they do then the new versions will be utilized for the changed drivers. Uninstall from the menu.
All tools are available from my Public Tools.
BTW, in case anyone forgot I wrote this tool to get rid of the multiple paragraph tags that Radio would insert into the upstreamed code whenever there were blank lines. [ Source: Surgical Diversions]

Fine-tuning Google Site Search

12:03:58 PM

comment []

More tips from RFB on fine-tuning the Google search box.

Sample code for focused custom Google search. The site search feature of Google's free custom search offering works by default only for sites whose addresses are root-level URLs (so, for example, you can use it out-of-the-box to search jrobb.userland.com or blogs.salon.com but not blogs.salon.com/0001111/).
With the help of Ian Landsman and a few other readers over the weekend, I've come up with code that produces a custom Google search of just this blog. I've in fact replaced my calendar with it (well, I've moved the calendar to the bottom of my masthead column anyway, on the theory that robots may still find it useful).
I want to offer the code to anyone to copy and tweak, but I've learned that posting code (even escaped-out code) to a blog entry tends to upset news aggregators, so instead I've written up the learning process with a few code samples as a story. [ Source: Radio Free Blogistan]

Google Search Specifics

11:58:42 AM

comment []

Repost: More details on how to force the Google search to stay within a given URL.

One solution to Google site search. Have I mentioned lately that I love the Internet? Cast a question on the waters and the answer (or an answer) generally comes back within 24 hours.
Ian Landsman sent me a solution in the comments to my previous post. I'd paste the code in here but even when escaped out it will cause problems for at least some aggregators, so look at the comment if you're interested.
Basically, Ian's solution passes the inurl:0001111 specification that limits the search to just my site on this server, including it in the query as a hidden text value by including name="q"
The only drawback I can see to this solution is that, by avoiding the custom Google search, it doesn't permit cobranding (not that big a deal to me as a private individual but perhaps an issue for more commercial enterprises) and it doesn't offer site-specific search option on the results page.
I'm playing around with a hybrid solution on an experimental page (experimental meaning undesigned, no navigation, etc.). Basically, it involves using as much of the custom code as possible but still trying to pass the hidden text values per Ian's solution. It seems to work just fine, but I'll keep banging away at it for a while to see if I've screwed it up.
If it does work, I'm going to replace my calendar with a search box and then probably write up a story with the code so it won't break aggregators but so I can distribute it to anyone who isn't blogging from the root of their domain.
(This entry x-posted to knowhow category because making blogs—or k-logs alike—searchable addresses a key question regarding the usefulness of logging as a KM or knowledge sharing instrument.) [ Source: Radio Free Blogistan]

Stupid #prefs.txt not found error

10:56:15 AM

comment []

Had to delete an entire day's worth of posts just to clear this up. This is a stupid error. I don't care if I caused it by putting in too many double quotes.

This is a stupid, brain-dead error message. That something so simple can crop up out of nowhere and you have no clue where to fix it is inexcusable. At least give me some way to find the error besides going backward through posts and killing them until the error goes away.