The forum search engine deems some terms such as "compound", "node" or "render" as too "common" to be searched for

Inspired by a tip that Stephen recently posted here, you can cheat around this by use wildcard searches such as:

rende* nod* compoun*

Note that wildcards have to be at the beginning or end of a search term

Fixing this on a permanent basis just got added to the "to do" list...
(or should we call it our "known issues" list?)

edit: owei and I have looked into it and while there seems to be an easy fix, this does involve some risk, owei rightfully doesn't want to take... So congratulations, rray, your workaround has now been promoted to "official fix" status.
(And your thread has been made a Sticky and your post has been copied to the "Read Me First")

would vote for being careful too, looking at XSIBase you can't help but notice there's enough malignant energy out there to make use of the smallest security pinhole.

As we weren't able to provide a better solution,
I took a minute to define an easily-bookmarkable (ad-based)
Google Custom Search Engine for our little community:
http://tinyurl.com/si-community

edit: Some of the posts following this one have been removed from this thread (posts by rray and myself). I tried a simple fix, rray helped to test it - thanks BTW -, we found out it didn't work, so I rolled back the "fix" and removed the discussion between rray and myself to avoid further confusion. For now, we'll have to live with rray's workaround (as this was the only harmless fix I could find)