Hi,

About the cron, I checked the BOLTFindex function, and it goes as follows:
    if ($args['rule'] != '') $out = BOLTindex($args['rule']);  // works 
through a rule if no list
    else {
        if (is_number($args['cron'])) {
So I don't see how rule and cron could be used at the same time...

In the end, I created several cron commands to page 
action.index&rule=rule1, action.index&rule=rule2 etc. The current rate is 
one every two minutes, each every twenty minutes (yes, I have quite a 
number of indexes). It works fine, using the default indexBatch value and 
updating the list of pages to be indexed everytime a change is made on the 
website by members.
I also added a "buildIndexes" script that I included with all the rules on 
a page I visit whenever I do massive changes from the FTP interface. Then I 
just have to way that the whole indexing has been processed by my index 
cron rules. If I know I will change main pages on a regular basis (use page 
not relevant at the moment, but you never know), I can also create a cron 
rule for this page. It spares me the necessity of login in and clicking my 
way through all indexes in action.index without starting the indexing 
process.
It is a simple copy from tha action.index indexing building form, and goes 
as follows (although I don't think it could be of use for anyone else):
code.script.inde
authkey: indexing
source: 'site.index::{?build}'
reset: search='{=source} fmt=list count=false dir=pages'
search:
[if set {?build}]edit: content='{=search}' page='site.index.{?build}'[if]
That's it,
Cheers,
Tiffany/Maelite




Le jeudi 7 janvier 2016 19:42:13 UTC+1, Dan a écrit :
>
> Thank you!. I fixed the typo, and moved the messages you indicated to 
> site.messages.
>
> As for #3, I believe you can use the cron parameter to do the equivalent. 
> Batch is probably a better word, but I'm not sure the change is worth the 
> disruption...
>
> [(index rule=site cron={?quantity})]
>
> Cheers,
> Dan
>
>
>
> On Tue, Jan 5, 2016 at 2:57 AM Tiffany Grenier <[email protected] 
> <javascript:>> wrote:
>
>> Hi,
>>
>> 3 quick notes regarding indexing:
>>
>>    - I just noticed a typo in BOLTindex:
>>    if ($myrule == '') return "Index rule //$myrule// not found";
>>    should be
>>    if ($myrule == '') return "Index rule //$rule// not found";
>>    Otherwise this warning gives no info at all...
>>    - Also, I think the "Indexing is current" and "No pages to index" 
>>    warnings should be localized and moved to site.messages.
>>    - And lastly, a small question: if I define 3 indexing rules and set 
>>    indexing to cron, nothing will happen, right? If so, could you please add 
>> a 
>>    "batch" parameter to the indexing function such that I can put in 
>>    cron.index (which is visited through a cron job):
>>    [(index rule=site batch={?quantity})]
>>    [(index rule=game batch={?quantity})]
>>    [(index rule=memberstats batch={?quantity})]
>>    I know it will kind of do that automaticaly everytime a page is 
>>    modified in the website, but i just modified a whole bunch of pages 
>> through 
>>    FTP and it's a real pain to re-index it all manually... I am heavily 
>> using 
>>    content of index.game and index.memberstats and need them up-to-date the 
>>    fastest way possible.
>>
>> Cheers,
>> Tiffany
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "BoltWire" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> Visit this group at https://groups.google.com/group/boltwire.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"BoltWire" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/boltwire.
For more options, visit https://groups.google.com/d/optout.

Reply via email to