Changes between Version 3 and Version 4 of TracTicketsCustomFields


Ignore:
Timestamp:
03/24/15 23:15:03 (2 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracTicketsCustomFields

    v3 v4  
    2020   * format: One of:
    2121     * `plain` for plain text
    22      * `wiki` to interpret the content as WikiFormatting
     22     * `wiki` to interpret the content as WikiFormatting (''since 0.11.3'')
    2323     * `reference` to treat the content as a queryable value (''since 1.0'')
    2424     * `list` to interpret the content as a list of queryable values, separated by whitespace (''since 1.0'')
     
    4040   * label: Descriptive label.
    4141   * value: Default text.
    42    * cols: Width in columns
     42   * cols: Width in columns.
    4343   * rows: Height in lines.
    4444   * order: Sort order placement.
    45    * format: Either `plain` for plain text or `wiki` to interpret the content as WikiFormatting.
    46 
    47 Macros will be expanded when rendering `textarea` fields with format `wiki`, but not when rendering `text` fields with format `wiki`.
     45   * format: Either `plain` for plain text or `wiki` to interpret the content as WikiFormatting. (''since 0.11.3'')
    4846
    4947=== Sample Config ===
     
    116114Note in particular the `LEFT OUTER JOIN` statement here.
    117115
    118 Note that if your config file uses an uppercase name, e.g.,
    119 {{{
    120 [ticket-custom]
    121 
    122 Progress_Type = text
    123 }}}
    124 you would use lowercase in the SQL:  `AND c.name = 'progress_type'`
    125 
    126116=== Updating the database ===
    127117