Changes between Version 53 and Version 54 of DateFieldPlugin

Timestamp:

Sep 14, 2015, 7:54:06 PM (9 years ago)

Author:

figaro

Comment:

Cosmetic changes

DateFieldPlugin

@@ -57 +57 @@
 }}}
  1. '''Configure''' the project management support for the plugin in its own configuration section, placed into 'trac.ini' file as follows: 
-    1. To add a Due Date, just set up the field as a [http://trac.edgewall.org/wiki/TracTicketsCustomFields custom field], or use the CustomFieldAdminPlugin (image right) to create a date field: [[Image(customfields.jpg, right, 20%)]]
+   1. To add a Due Date, just set up the field as a [http://trac.edgewall.org/wiki/TracTicketsCustomFields custom field], or use the CustomFieldAdminPlugin (image right) to create a date field: [[Image(customfields.jpg, right, 20%)]]
  {{{#!ini
 [ticket-custom]
@@ -66 +66 @@
 due_date.date_empty = true
 }}}
- The example demonstrated use of the special value `<now>`, which is supported only on the 1.0 branch. The value will be replaced with the current date.
-    1. Site-wide defaults for macro arguments may be set at [datefield] section. More details about them see [#Arguments #Arguments section].
+   The example demonstrated use of the special value `<now>`, which is supported only on the 1.0 branch. The value will be replaced with the current date.
+   1. Site-wide defaults for macro arguments may be set at the [datefield] section:
 {{{#!ini
 [datefield]
@@ -74 +74 @@
 first_day = 1
 }}}
+   More details about them see [#Arguments #Arguments section].
  1. '''Restart''' web server on command line:
 {{{#!sh