Thanks, this works except the title. I am not sure if it's my code or
a bug.
[t]
[(search group=test.* fmt="[r][c style='width:150px;padding:
0;']>>{+p5}.{+p4}.{+p3} – {+p6}:{+p7}>>[c style='padding:0;'][[{+p}|
{+p:title}]]")]
[t]
{+p:title} is displayed as "{+p:title}". If I only try with {:title},
I get the title of the current page inserted for each result – as
expected.
Markus
PS: Good to hear that you are having days full of incredible joy and
pleasure with BoltWire these days. ;)
On Mar 12, 12:45 pm, The Editor <[email protected]> wrote:
> Oh sorry. That was one thing I fixed that broke something else which I
> fixed and didn't realize this broke again. I'm having some real
> conundrums with this change. Honest I had it fixed at one point...
>
> Temporarily you can do it this way which is probably faster anyway:
>
> [t]
> [(search group=test fmt="[r][c
> style='width:150px;padding:0;']>><(lastmodified page={+p}
> fmt='%d.%m.%Y – %H:%M')>>>[c style='width:400px;padding:0;']
> <(breadcrumb {+p} offset=1 name=link)>")]
> [t]
>
> The problem is the new table markup, which handles the whole table
> rather than individual tags. Which was necessary to get the line
> spacing to generate proper html. But unfortunately this doesn't work
> in templates. I'll have to find some other solution...
>
> Ah, I have an idea. Make the line spacing program much smarter--by
> handling all the internal line spacing of things like tables and boxes
> and the like at that time. And keep all the markups simpler rules.
> Just move the algorithms. It will take some work, but it would solve
> all these complexities I keep bumping into perhaps.
>
> Hey for that matter I think I have solution for a double encoding
> problem of htmlspecial chars as well. Exciting. Back to the
> engineering table.
>
> Cheers,
> Dan
>
>
>
> On Fri, Mar 12, 2010 at 4:32 AM, Markus <[email protected]> wrote:
> > 1) Template displays as markup:
>
> > [t]
> > [r]
> > [c style="width:150px;padding:0;"]09.03.2010 – 23:24
> > [c style="padding:0;"]...
>
> > The template is:
>
> > [(template first)][t]
> > [(template each)][r]
> > [c style="width:150px;padding:0;"]>>{+p5}.{+p4}.{+p3} – {+p6}:{+p7}>>
> > [c style="padding:0;"][[{+p}|{+:title}]]
> > [(template last)][t]
> > [[#end]]
>
> > 2) A line "->**text**<-" displays as markup too.
>
> > On Mar 12, 12:35 am, The Editor <[email protected]> wrote:
> >> Just released another stab at getting the line spacing problem right.
> >> The main vspace engine seems to be working quite well. But getting all
> >> the possible things you can get BoltWire to do properly hooked up to
> >> it is another story. I've also found several security glitches
> >> introduced by the change in our character encoding scheme for 3.4,
> >> that I've been trying to patch. I have a system going for these kinds
> >> of problems now, but it's like chasing your tail. You fix one thing
> >> and something else breaks. You fix it, and the first thing goes out
> >> again. But at least we have things down to one or two critical point
> >> in the code. So it's getting easier.
>
> >>http://www.boltwire.com/files/boltwire3.4.3.zip
>
> >> From the changelog:
>
> >> * Expanded zones, code zones, and snippets to match -, _, letters, &
> >> numbers.
> >> * More reworking of code to remove bugs and patch security of the core
> >> for the new linespacing code. Extensive work with diffs, stamps,
> >> templates, boxes, etc.
>
> >> This release involved lot's of tweaks so if everything still works I'd
> >> be surprized. But some of our reported bugs are cleared back up again.
> >> :)
>
> >> 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
> > athttp://groups.google.com/group/boltwire?hl=en.
--
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.
