My suggestion is simply to add a
inputString = strreplace( ' ', '_', inputString );
in the data function. The {::variable} will act much as it does not,
while the data function will be internally consistent, treating
"one_two" the same as "one two".
On Jul 27, 6:52 pm, Martin <[email protected]> wrote:
> Does this mean you have a solution for this problem that you reported
> first?
>
> If so, can you tell us about?
>
> Greetings, Martin
>
> On Jul 27, 12:51 pm, DrunkenMonk <[email protected]> wrote:
>
> > If it does, the info function may become much slower on some pages, as
> > it will have to search through paragraphs to find possible info
> > variables.
>
> > However, this could be solved by running the field through a search
> > and replace...
>
> > On Jul 27, 7:16 am, Martin <[email protected]> wrote:
>
> > > info should take all characters up to the first ":" as field.
>
> > > It does not. It takes only the first word and scramble the results
> > > when two words
> > > are found.
>
> > > [(template each)][(info target=info.test field="{+::item}" value=+
> > > {+p})]
>
> > > Results:
>
> > > one_word: value1,value2 => fine
> > > two words: value1value2 => not good
>
> > > Greetings, Martin
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
