Issue Bug Closed

#42252EM incorrectly parses extension configuration options

Andreas Wolf 10/21/12, 19:38 updated 10/23/17, 22:14

Description

The ConfigurationItemRepository dissects the ext_conf_template.txt file to get all available configuration options. For “options” type items, the format is interpreted in a wrong way. The string in ext_conf_template will look like this (taken from EXT:tika):

  # cat=basic//10; type=options[Tika (local java application)=tika,Solr (remote server)=solr]; label= Extract using: Extraction will be faster if run locally using Tika.

The ConfigurationItemRepository incorrectly assumes that the option values are stored in the square brackets, while the labels for these options would be in (imaginary) square brackets after “label=”.

The ExtJS-based EM uses the correct approach here.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.