Custom Query (332 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (61 - 63 of 332)

Ticket Resolution Summary Owner Reporter
#99 fixed RFC 3676 support breaks when content-type doesn't include delsp parameter bas ben@…
Description

A fix for content=flowed support, makes it work correctly when the user agent doesn't provide the delsp param in the Content-Type header.

#101 fixed Correctly set custom field default values when creating a ticket bas ben@…
Description

Currently, all ticket custom fields are set to None instead of their proper default values when a ticket is created by email2trac. The patch below fixes the problem

--- email2trac.py.in.txt (saved version)
+++ (current document)
@@ -682,7 +682,13 @@
 
 			# default trac value
 			#
-			value = self.get_config('ticket', 'default_%s' %(name) )
+			if not field.get('custom'):
+				value = self.get_config('ticket', 'default_%s' %(name) )
+			else:
+				value = field.get('value')
+				options = field.get('options')
+				if value and options and value not in options:
+					value = options[int(value)]
 			if self.DEBUG > 10:
 				print 'trac.ini name %s = %s' %(name, value)
 
#106 fixed More versatile support for Mac attachments bas ben@…
Description

I implemented three new configuration options, having to do with treatment of attachments that include Mac-specific data.

The attached diff is relative to the changes I submitted in #105.

binhex

The BinHex encoding format is deprecated (in favor of AppleDouble MIME, see RFC 1740), but some older clients might still be using it. A file encoded with BinHex is annoying to decode unless you are on a Mac.

The binhex option can be set to one of:

  • 'keep', in which case attachments encoded with BinHex will be included in the ticket
  • 'warn', in which case attachments encoded with BinHex will be ignored, but a warning message to that effect will be included in the ticket description
  • 'drop', in which case attachments encoded with BinHex will be silently ignored

The default is 'warn'.

applesingle

Same options and meaning as for binhex option above.

appledouble

The AppleDouble encoding format is the recommended way to include Mac-specific data in a MIME message, as per RFC 1740. A file encoded with AppleDouble can easily be presented usefully on all platforms.

The applesingle option can be set to one of:

  • 'keep', in which case both the platform-neutral data and the Mac-specific data will be included in the ticket (as two separate attachments)
  • 'warn', in which case only the platform-neutral file data will be included in the ticket. Mac-specific data will be left out, but a warning message will be included in the ticket description.
  • 'strip', in which case only the platform-neutral file data will be included in the ticket. Mac-specific data will be left out with no warning.

The default is 'warn'.

Note: See TracQuery for help on using queries.