[greenstone-devel] FYI: conditional expressions not interpreted (was: Greenstone 2.61 released!)

From jens wille
DateTue, 27 Sep 2005 21:40:26 +0200
Subject [greenstone-devel] FYI: conditional expressions not interpreted (was: Greenstone 2.61 released!)
In-Reply-To (42FC1C4C-90701-cs-waikato-ac-nz)
hi!

just to let you know...

Katherine Don wrote:
> - collectionmeta now accessed from the config file, not the
> database - no longer need to rebuild the collection when changing
> collectionmeta.
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?).

a workaround is to insert a custom macro and define it in extra.dm
(which is what i used to do anyway to be able to change my
collectionmeta without the need to rebuild the collection even with
versions prior to 2.61)

apart from that, as far as i can tell (mainly regarding command-line
building covering mg, HTMLPlug, AZCompactList and Hierarchy), the
new version is doing well.

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

cheers
jens