Just a quick off the cuff response without really testing this...
(0) The php problem is most likely something to do with your custom script
(though I am still finding bugs in the 4.xx series). If you want to post it
or email it I'll take a look. I do however use nested functions like that
all the time. There is no way to get a variable to return changing
values--that's the essential difference between variables and functions.
You can however do something like this in config.php:
$BOLTvar['myvar'] = somefunction();
{myvar} will have the same value throughout the page, but it can be
anything the function generates.
(1) Not sure how you are using the print action but if it is a link you can
do something like [[some.page&action=print&myvar={?myvar}|Label]]. That
will pass the var on to the next page. I have whole sections of my site
that constantly pass get variables around like that--though in other cases
its easier to use data variables or even cookies. BoltWire can use any of
those approaches.
(2) As for the fmt problem--I need a bit more information to figure out
what the problem is. Is the output supposed to be an upload markup like
[^img.jpg rel=lightbox data-lightbox={+p}^] or something else? The allowed
attributes are defined in variables.php. To change one of them, try adding
a line like the following in config.php (adding rel and data-lightbox to
the list of course):
$BOLTattrs['img'] =
'align,border,style,class,height,width,hspace,vspace,title,alt'; // this
is the default, change as needed
(3) Try adding join=' ' to the search parameter to change the divider
between hits from a line return to a space. Let me know if that doesn't
work.
Cheers,
Dan
On Fri, Feb 28, 2014 at 2:05 AM, jdoe <[email protected]>wrote:
> Hello Dan & thanks for looking into this,
>
> unfortunately php breaks (i.e. produces the classical blank screen that
> occurs when syntax fails) when using the suggested syntax (with and without
> the single quotes, and irrespective of <>{}[] mode). Too, 'thefunction'
> yields different results whenever it is called, so I still think it would
> be neat to assign the return value to a variable.
> - Would you still see a way to do this?
>
>
> On a related note, I observed some few other things, which should probably
> work:
>
> (1) when calling a page assigning a get-variable (i.e.
> https://www.somesite.com/thewiki/index.php?p=somepage&thevar=someexpression),
> the get-call (and by consequence thevar) is lost when calling the print
> action, which results in not rendering thevar-based output.
>
> (2) in the fmt-bit of the described search function, when adding either
> rel='lightbox'or data-lightbox='{+p}' (since the most recent version),
> this syntax is ignored. As this seems to have worked in the past after
> reading some earlier BoltWire notes, I wonder where I'm going wrong here.
>
> (3) search results of the described search function are appended and
> rendered inserting line breaks (<br>) between items. Is there a way to have
> this rendered just using e.g. a space?
>
> Thanks & regards,
> JF
>
> --
> 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 http://groups.google.com/group/boltwire.
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
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 http://groups.google.com/group/boltwire.
For more options, visit https://groups.google.com/groups/opt_out.
