Linly, I think this happened when I piped the info vars function
through search's sort function, because it required me to keep the
keys in the output array. (That may not make sense). Anyway, after
nosing around, I noticed the {count} {prev} and {next} vars were also
all broken, and possibly others--as a result. To make a long story
short, I spent a good bit of time tinkering and came up with not only
a fix but some nice features. Still working on it, but now you have:
1). An {+index} var which gives the index of the hit in the original
search page list (before being shuffled, or sorted or the like).
Everything bumped up so hit #1 is #1, #2 is #2, etc.
2). I added a {+field}, {+value} variable to the info report function,
with {+field} = {+p} and {+value} = {+index}, or {info.page::{+p}}.
Very handy. In fact, the function just translates these two in the
template. Field and Value are not available in search templates, only
info reports. Though you do have index and p of course.
As with the other special vars, none of these are available in the fmt
function. I'll put out the new release shortly. I can't seem to find
any more of the line spacing problems, so I guess they are either all
gone or not worth worrying about. Everything is looking pretty good.
Cheers,
Dan
2009/4/2 Linly <[email protected]>:
>
> This one worked:
>
> [(info report target=info.main.news sort=lastmodified fmt=title)]
>
> But adding "count=5", it broken:
>
> [(info report target=info.main.news sort=lastmodified count=5
> fmt=title)]
>
> But I have another site using "count=" is ok:
>
> [(info report count=10 order=reverse sort=value target=info.wikiblog
> fmt=title)]
>
> So I took off the "sort=lastmodified" and it work again:
>
> [(info report target=info.main.news count=5 fmt=title)]
>
> So the problem is between the two parameters: "count=5" and
> "sort=lastmodified". They can work along not together.
>
> Cheers, linly
>
> On 4月2日, 上午11時05分, Linly <[email protected]> wrote:
>> I suddenly found that the info report parameter "count=" is broken. No
>> matter I set to what number, it returned p=0.
>>
>> Cheers, linly
>>
>> On 4月2日, 上午2時40分, The Editor <[email protected]> wrote:
>>
>> > Latest News: Just out is version 2.72, with a minor fix to rss
>> > handling and a bug fix involving var functions, like {( )}. A pretty
>> > serious bug--knocked out I guess in 2.71 I think--which is why I
>> > wanted to rush this out even though the change list is slim. Also, I
>> > still have had time to debug the line returns being eaten here and
>> > there (I just need some time to track it down).
>>
>> > Sorry for the delay, but 3.xx really is just ahead!!! We've got a
>> > seemingly pretty stable release, now. All I need is a bit of free time
>> > for the big switch, as I want some time available to help fix custom
>> > scripts & plugins should there be any problems when that switch does
>> > come.
>>
>> > Cheers,
>> > Dan
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
