Bugs/Feature Requests

Development News

Version 0.5dev of this plugin is now available. The 0.11 branch is undergoing frequent change. If you want to test out the latest version, report back how it is working and possibly do some debugging, then the latest version is for you. Otherwise, r11004 should be fairly stable.

The autocomplete list can be attached to a text-based field other than the Keywords field (#5831).

The helppage link can point to any resource in any realm. For example, it can be a link to the /tags page. Previously, it could only point to a wiki page (#5907).

Several bug fixes.

Compatibility notes:

Previously, the multipleseparator configuration option was defined in quotes (e.g. ", "). Now, only the separator character should be specified (e.g. multipleseparator = ,).

Several of the configuration options will be renamed before 0.5 is released. Please revisit this section for additional notes before installing a new version.

Planned enhancements before 0.5 is released:

Allow the autocomplete list to be attached to more than one text-based ticket field. Additionally, different configurations will be supported for each ticket field. For example, one of the ticket fields could be using keywords from the TagsPlugin and the other could be using keywords defined in trac.ini (#5831).

A new boolean option usetagsplugin. Currently, the TagsPlugin will be used when it is installed and enabled.

Offer all keywords used up until now for use, even if the TagsPlugin is not installed (#3816).

There is the possibility of supporting multiple themes (​comment:8:ticket:8141). Please comment in that ticket if you have any thoughts on the issue.

Strip single quotes from the multipleseparatorOption value. This allows the user to specify a single whitespace separator as ' ' (which is not necessary since a single whitespace is the default), or even dream up separators such as double whitespace as ' '. A single whitespace character is used as the separator in the case the user specifies ''. Thanks to itamarost for pointing out this corner case in his original patch.

Wired up unit tests.

Renamed keywords.py to web_ui.py, to work around an issue described in comment:39, in which the keywordsuggest.keywordsuggest module was not being found by the keywordsuggest.tests.keywordsuggest module when running unit tests.

NOTE: If you have enabled the plugin through webadmin or by editing trac.ini with keywordsuggest.keywordsuggest.* = enabled, you will need to re-enable the plugin through webadmin, or edit the line to keywordsuggest.web_ui.* = enabled (or keywordsuggest.web_ui.keywordsuggestmodule = enabled).