Omegascript $set{stem_all,true} affects $field processing

[Mike Hsu]

When an Omegascript template contains the command $set{stem_all,true}, later references to $field{XXX} return nothing.

This appears to be caused by new "fieldnames" processing introduced in 0.9.3 The code in print_caption() in query.cc obtains an iterator to a "fieldnames" option via

opt = option.lower_bound("fieldnames");

But because there is currently no default "fieldnames" option, if there is no "fieldnames" option set in Omegascript, lower_bound will return an iterator pointing to the "stem_all" option. This is then incorrectly processed as the "fieldnames" option, and if it has a non-null value, the "field" map is never loaded.

The short-term workaround is to include a $set{fieldnames,} command in the template, if it isn't already being used for something.

[Olly Betts]

Proposed fix

[Olly Betts]

Yes, your analysis is spot on!

Could you try the attached patch?

[Mike Hsu]

Looks good, thanks Olly!

[Olly Betts]

Thanks for testing.

Fixed in SVN trunk.

[Olly Betts]

Fixed in 0.9.5