Changes between Version 12 and Version 13 of CondFieldsGenshiPlugin
- Timestamp:
- Jul 15, 2015, 1:24:53 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CondFieldsGenshiPlugin
v12 v13 5 5 == Description 6 6 7 With the help of this Trac plugin you canhide or show fields when creating or viewing a ticket, depending on the ticket type. Only the7 This plugin allows you to hide or show fields when creating or viewing a ticket, depending on the ticket type. Only the 8 8 presentation changes, not the contents of the ticket. 9 9 10 CondFieldsGenshiPlugin is derived from the CondFieldsPlugin, but it is completely based on Genshi nowinstead of using Javascript. Moreover, you can select whether selected fields are hidden or shown by default.10 CondFieldsGenshiPlugin is derived from the CondFieldsPlugin, with the difference that it is completely based on Genshi instead of using Javascript. Moreover, you can select whether selected fields are hidden or shown by default. 11 11 12 12 This plugin is standalone; the patch `blackmagic-conditionalfields.patch` in #2486 did not match with newer releases of Trac 0.11. … … 14 14 Some problems reported about the more powerful DynamicFieldsPlugin (bad scaling for many fields, malfunction if fields are internally sorted, clearing value of hidden fields) should not occur here. 15 15 16 It should be easy to extend this plugin, eg for dependence on other parametersthan ticket type.16 It should be easy to extend this plugin, eg for dependence on parameters other than ticket type. 17 17 18 18 The plugin was tested under Trac 0.11 and 0.12. … … 38 38 == Configuration 39 39 40 First, configure the`trac.ini` file as in this example:40 First, configure your `trac.ini` file as in this example: 41 41 42 {{{ 43 #!ini 42 {{{#!ini 44 43 [components] 45 44 condfieldsgenshi.* = enabled … … 61 60 62 61 The entry: 63 {{{ 64 #!ini 65 default = disable 66 }}} 62 {{{#!ini 63 default = disable 64 }}} 67 65 68 66 means that the field listed under tweaks are '''not''' shown by default. … … 71 69 72 70 To disable/enable a field independent of the ticket type, simply write a line like: 73 {{{ 74 #!ini 75 field1.type_cond = None 76 }}} 71 {{{#!ini 72 field1.type_cond = None 73 }}} 77 74 78 75 Supposing there is no None type. … … 84 81 When the ticket type is given as an URL parameter only: 85 82 86 .../newticket?type=task83 `.../newticket?type=task` 87 84 88 85 and the ticket type field is disabled, this plugin works nevertheless, in contrast to the CondFieldsPlugin.