I’ve uploaded new pages with new (working!) Google site search in the footer of each page. Content is the same but uses the new Google search code. Sorry about the ads in the results - I can’t avoid that inclusion as it’s done at the server end.
Incidentally, does anyone use the (Google) Translate widget I put in each page. I’ve no idea how good the translation is. Given the amount of technical (And Tinderbox) terminology I suspect it may not always help. I’d be interested to hear.
Sorry, Google broke (changed function of?) their search again, and I’ve no idea as to how to fix it. most likely I’ll sadly have to remove the search when I next do a full site update. I did fix it once before which simply involved a new block of code. this breakage seems different.
If anyone does know how to fix this, I’m open to suggestions.
One workaround for now is aTbREf’s sitemap (aTbRef Site Map). There is a link for this at the top and bottom of every page. Although it only lists page titles you can use your web browser’s ‘find’ feature to search the page.
Also for action codes like collect_if() in your screen-grab, it is only 2 clicks from front page to the article. Front page, top of screen, click ‘action codes’, scroll page and click ‘collect_if’.
The main site is updated with the current public release (see front page of the site). Some pages get interim updates which may—as a beta tester—get done using the current beta which may report as a later version than current.
You’d need to ask Eastgate directly. By the convention of this forum we don’t discuss the details of betas & release schedules (at least everyone bar Eastgate!).
