Search options (Page 41 of 77)

So does that relate specifically to the search cache/index tables themselves, then, and not searching the db directly as in the multibyte? method.

You can't. The search function works on each word separately, as is.

MySQL only, or PgSQL too? I would have thought that would be down to input parsing rather than db type.

Glad you like it.

The beauty of it is the fact that very little extra code is needed, and all it does is use the multibyte method of searching, so nothing changes with regards to how the search function works. Plus, one still has the option of doing searches the old fashioned way.

Well, once I figured out the search cache/table was killing the full string searches, it seems I have a working one for testing with. It needs one extra entry in lang/[language]/search.php:

'Search full'   =>    'Search for the complete string as entered. [ If not selected, each word entered will be searched for separately. ]',

and here's the link to the file:

http://outgoing.bauchan.org/unix/search.txt

I've only given it a quick test, but it appears to be working as expected. If the full string checkbox isn't selected/ticked, it defaults back to the standard way of searching.

Oops. I never noticed that trailing slash missing. Must admit, I always use the <img ... /> method.

Can't fault that reasoning.

Would it not be a worthwhile addition, however, to the search function, to make an option in the search box, (i.e: if someone can remember a snippet from a thread, and they wish to hone the search), would it not be better to have a checkbox that would do a full string search only, if selected, and a split keyword search if not?

Alter the two queries in include/functions which set the pun_user array to fetch the info from your table as well as the user table. Personally, I'd create a separate array and leave the pun_user array and db query as is, but the choice is yours.

I believe they were debating the placement, i.e: src alt versus alt src.

Elbekko, mind if I brainpick over that code?

Firstly, does this line:

$userinfo[$cur_feed['rssfeed']] = $cur_feed;

fetch the items from the db info, and then place them into an array of the likes of:

$userinfo[the feed url][id]
$userinfo[the feed url][firstname]
$userinfo[the feed url][username]
$userinfo[the feed url][rssfeed]

?

Secondly, this line:

$info = $userinfo[$item->feed->feed_url];

How exactly does that item->feed->feed_url bit work? Is that a key as stored in the first_items array, or other?

Just trying to broaden my grasp of the multi-dimensional arrays. These devils have always eluded me thus far.

Cheers,

Matt