Re: [greenstone-devel] FYI: conditional expressions not interpreted

From Katherine Don
DateWed, 28 Sep 2005 16:13:52 +1200
Subject Re: [greenstone-devel] FYI: conditional expressions not interpreted
In-Reply-To (4339A02A-1060804-gmx-net)
Hi jens
>>- collectionmeta now accessed from the config file, not the
>>database - no longer need to rebuild the collection when changing
> i'm not sure if it's a bug or a feature ;-) but now conditional
> expressions ( or {If}) aren't interpreted (correctly) in the
> collectionextra statement. the former always evaluates to
> action-if-true (tried different '"_macro_" eq "value"'s), while the
> latter just gets displayed as-is (was that even possible in the past?).
You can't use {If}{...} in collectionextra - {If} is only valid for
format statements.
should work, but the way its set up at the moment, it has to be
like true
And when you enter it in the gli, it gets written to the config file
like true
(with " instead of " )
and this doesn't work. I'll fix this for the next release, but in the
meantime, you can edit the collect.cfg file by hand, and put single
quotes around collectionextra, and change " in statements to ".

> anyway, greenstone is great work - and it's constantly getting
> better. kudos to all the developers!
thanks :-)