On Mar 12, 6:19 pm, The Editor <[email protected]> wrote:
> On Fri, Mar 12, 2010 at 11:15 AM, Markus <[email protected]> wrote:
> > 1) The code you pointed me to in the other thread lost even more
> > functionality:
>
> > [t]
> > [(search group=test.* fmt="[r][c]>>{+p5}.{+p4}.{+p3} – {+p6}:{+p7}>>[c]
> > [[{+p}|{+p:title}]]")]
> > [t]
>
> > .. – : the title
> > .. – : the title
> > .. – : the title
> > ...
>
> Ok, there was a bug with this. Fixed now...
>
> However note, {+p:title} won't work in a fmt anyway. Should be changed
> to [[{+p}|+]]
>
> On the other hand, now you can run your original template. That's what
> I was trying to fix primarily. Didn't think to check the fmt's though
> I should of realized all that tinkering would affect them too...
I liked the idea of using fmt. I wondered if I could just add this to
code.snippets:
myfmt: "[r][c]>>{+p5}.{+p4}.{+p3} – {+p6}:{+p7}>>[c][[{+p}|+]]"
And use it with:
[t]
[(search group=test.* fmt=$$myfmt)]
[t]
But then I am back to: .. – : title of current page
If that does not work on purpose or by design, just ignore it. Just
wanted to tell you in case you need to know. I am fine with two
working solutions. :)
> > 2) Still: ->not working<-
>
> The markups for this was changed sometime back. Perhaps recently. Now
> you must have
>
> ->
> working
> <-
>
> The indent markups should go on their own line to match the pattern.
> My reason is I don't want to accidently match a -> people might put in
> their text. If you prefer the old markup rule, you could always reset
> it in config.php. I could give you the code if you like.
>
> > 3) [(search group=test.*)] -> the server unexpectedly dropped the
> > connection", it seems to only work when there are no search results.
>
> This seems to be working fine for me, though it is possible the fix
> from #1 above was involved. Let me know if the new download (still
> 3.4.4) doesn't resolve this as well as the other problems.
Seems to be fixed.
> I also fixed another little glitch, where the Preview/Submit buttons
> were scooted to the side of the textarea box on several action forms.
I was already cheering that preview would work again... but take your
time. :)
I still see that button bug here:
[(popup link="...fancylink..." label=[^fancylabel^] height=348
width=758 resizable=false)]
(Text)
"(Text)" is next to the image.
>
> I'm encouraged that these were all easy to fix. Reassures me the
> mechanisms we have in place can solve our problems. Thanks for all
> your prompt help with the testing. We should be getting close to the
> end of this linespacing problem...
Yes, after searching and replacing about a thousand times my sites
seem to be running pretty fine again. (Until I notice what I
accidentally replaced... :)
Oh, and thanks that you consciously or not made it possible to use
<box> and <code> inline or as a paragraph without getting additional
line breaks in the latter case.
>
> http://www.boltwire.com/files/boltwire3.4.4.zip(again)
>
> Cheers,
> Dan
On Mar 12, 6:19 pm, The Editor <[email protected]> wrote:
> On Fri, Mar 12, 2010 at 11:15 AM, Markus <[email protected]> wrote:
> > 1) The code you pointed me to in the other thread lost even more
> > functionality:
>
> > [t]
> > [(search group=test.* fmt="[r][c]>>{+p5}.{+p4}.{+p3} – {+p6}:{+p7}>>[c]
> > [[{+p}|{+p:title}]]")]
> > [t]
>
> > .. – : the title
> > .. – : the title
> > .. – : the title
> > ...
>
> Ok, there was a bug with this. Fixed now...
>
> However note, {+p:title} won't work in a fmt anyway. Should be changed
> to [[{+p}|+]]
>
> On the other hand, now you can run your original template. That's what
> I was trying to fix primarily. Didn't think to check the fmt's though
> I should of realized all that tinkering would affect them too...
>
> > 2) Still: ->not working<-
>
> The markups for this was changed sometime back. Perhaps recently. Now
> you must have
>
> ->
> working
> <-
>
> The indent markups should go on their own line to match the pattern.
> My reason is I don't want to accidently match a -> people might put in
> their text. If you prefer the old markup rule, you could always reset
> it in config.php. I could give you the code if you like.
>
> > 3) [(search group=test.*)] -> the server unexpectedly dropped the
> > connection", it seems to only work when there are no search results.
>
> This seems to be working fine for me, though it is possible the fix
> from #1 above was involved. Let me know if the new download (still
> 3.4.4) doesn't resolve this as well as the other problems.
>
> I also fixed another little glitch, where the Preview/Submit buttons
> were scooted to the side of the textarea box on several action forms.
>
> I'm encouraged that these were all easy to fix. Reassures me the
> mechanisms we have in place can solve our problems. Thanks for all
> your prompt help with the testing. We should be getting close to the
> end of this linespacing problem...
>
> http://www.boltwire.com/files/boltwire3.4.4.zip(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 at
http://groups.google.com/group/boltwire?hl=en.
