Release notes for WebAPI 3.11.0.4203

Bug fixes

Cache files of images would be created in the same format as the original (like .tif) even when a .bmp format version of the cached file was already present. This was fixed in 3.10.1.4180.
The WebAPI writecontent command would replace a + sign in a file name by a space. Fixed in 3.10.1.4186. Note that you can only use both + and white space characters in file names if you enclose the value in double quotes. For use in Collections (in retrieval paths and storage paths) you should then wrap the %data% placeholder in double quotes: "%data%". It's best of course, to not use + or white space characters in media file names.
The WebAPI diagnostics output could contain sensitive information. This was fixed in version 3.10.1.4165.
There was an incorrect Magick.NET.Core bindingRedirect in the web.config. Fixed in version 3.10.1.4158.
A "The method or operation is not implemented" error was generated when retrieving images using the generic Media Server plugin. Fixed in 3.10.1.4132..
There were different results for a q-search and an equals search when searching for a comma-separated list of terms (with Full Text indexing disabled): the q-search treated the list as a single value. This was fixed in 3.10.1.4097.
The Pictura (Memorix) image plugin no longer worked with the latest API: the plugin failed to load the configuration from adlibweb.xml. Fixed in version 3.10.1.4086. Some changes in the WebAPI now force the image plugin element to upper case and the value in the type attribute like this:
<ImagePlugin type="Adlib.Pictura.Imaging.Plugin.PicturaImagePlugin, Pictura.Image.Plugin">
(Previously, this was: <imagePlugin type="Adlib.Pictura.Imaging.Plugin.PicturaImagePlugin, PicturaImagePlugin">)
Insertrecord did not save indexed links. Fixed in 3.10.1.4079.
The adlibweb.sample.xml <logFolder> element example wasn't complete. This was fixed in version 3.10.1.4071 and is now:
<logFolder InputLog="WebApiInputLog.${date:format=yyyy-MM-dd}.txt" OutputLog="WebApiOutputLog.${date:format=yyyy-MM-dd}.txt" MaxOldFiles="10" Level="Debug">.\Logs</logFolder>

<debug>false</debug>

New functionality

Media lookup field feature for all media plugins

If the field value to retrieve a media file from a DAMS is different from the field value which the WebAPI must use in a getcontent call, then you can now use lookup field functionality, where an "input" field designates the public (visible) field and an output field the field which contains the value that must be used by the media plugin to actually find the file in the DAMS. This can be configured in the imageServerConfiguration in adlibweb.xml with the following configuration elements. All three must be present for the lookup feature to be enabled. You can use English field names or field tags and for the database use the name of the .inf (without the file extension) containing these fields. For example:

<idLookupDatabase>media</idLookupDatabase>            

<idLookupInputField>FN</idLookupInputField>            

<idLookupOutputField>guid</idLookupOutputField>

This is functional for any media plugin. Because this lookup is done before a plugin is called, no changes have to be made to the plugin configurations. The plugin will just receive the new id/value and will function as usual.

Setting to disable rendition override added to Piction image plugin

Via a URL, end-users have the option to load a higher rendition than allowed. To disable this override option and have users always retrieve the configured rendition, you may add the following new setting inside the ImagePlugin node:

This option is only functional for version 2 of the image plugin.

More logging added to the Axiell generic Media Server plugin

For the writecontent command in particular, more logging was added to allow better analysis if a writecontent command is not processed as expected. Available from version 3.10.1.4093.