I haven't started looking at the issue Martin brought up about a max
file index size but after re-reading this again, Drunken Monk may be
right. Doesn't say anywhere that you reindexed the page...
BoltWire doesn't scan your folder for unindexed pages, modified
pages, or even deleted pages. (Perhaps this should be worked on...)
Rather, you have to tell it to index certain pages. Normally, if
editing or renaming is done within the wiki this is handled
automatically. But for something like what you have done, you need to
generate that list. This can be done by going to site.index and
clicking the button. Then continue refreshing the page till everything
is done. If you can parameterize the pages you want to index somehow
(group=login, etc) , edit the search command of the form on
site.index and then click the button. No need to reindex the whole
site.
That's assuming the system works properly. So I thought I'd give it a
good test to see if it was working. Turns out there was a bug after
all. When doing a search command, the form sends it's parameters
directly over to the search function, bypassing the normal BOLTMfunc
function which handles all output options. So the normal index
generation form creates some mildly funky output. Which evidently
interferes with the indexing. Voila!
The easy fix is this: change commands.php around line 506 to add this
little condition:
if ($args['output'] != 'escape') $query = BOLTdomarkup($query);
However, again I'm not sure this is the best fix. Because the same
thing would happen to any other function called directly like this, or
even through BOLTcomm2func. The better solution would be to have the
search function go through BOLTcomm2func and then have BOLTcomm2func
call BOLTMfunc to get all of the features available there (like
output, and toolmapping, etc)... Which is not particularly hard, but
it does do a bit of rewiring under the hood. With potentials for
problems here and there...
But the best way is always the right way, wouldn't you think?
One other little problem thrown in--the login function taps into the
BOLTXsearch function using a special $auth parameter to allow you to
scan pages you may not have auth to view. This is done to allow you to
search for an email address and login that way, rather than by id. But
it was possible to work around that--by reshaping the login code just
a bit and sending it to BOLTFsearch instead...
But in testing that I found another bug no one has yet reported...
Count is executed before checking for matches to text, data, or
links... Meaning, options can get cut off before examined. Not good...
Why has no one noticed this before? Curious...
Now how to fix it... More logically the count= code should go into the
display function, shouldn't it? Yes, that should solve it without too
much trouble. For that matter, thinking about it semantically,
shouldn't: include, exclude, type, if, etc all go into the
BOLTsearchpagelist function as these determine which pages in the page
list? And only sort and order go in BOLTsort as these affect order?
And count goes in display as it controls which results are shown--more
importantly, it's done after the list has all been checked for
matches... Ok a bit of reshuffling though not any real new code. I
got it all hooked up in no time. Just need some more testing now to
make sure it works...
Ok, all looks good. Logging in by email. Etc. BTW, I just added a
couple lines to the register command that checks an entered email
address to make sure it is unique. At least at time of registration,
given all indexed pages...
I think that's about got this problem fixed. I'll post a new release
later on today. Just a bit more testing first. Let's call this next
release experimental!
Cheers
Dan
P.S. Martin, please tell me if this fixes your indexing issues. Sorry
for not catching this sooner...
On Wed, Aug 5, 2009 at 1:33 AM, JJ<[email protected]> wrote:
>
> Hello:
>
> I recently renamed some of my pages manually from c-li.
> When I went to search in my site for grep_parsed.log it wasn't found.
> grep'ing from c-li showed me the page that had it.
>
> I went to action.index and tried a "blank" in the field and hit enter.
> I tried * in the field and hit enter.
>
> Site Search will not find it but once.
> P.S. Searched here for indexes, (and correctly indices) and indexing,
> but not much luck.
>
> What am I missing?
> Thanks for your time.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---
