﻿ticket	summary	type	release	owner	status	created	modified	_description	_reporter
12518	Implement new notification API	task	1.0	Franz	new	2015-09-21T08:50:57+02:00	2015-09-21T09:34:31+02:00	"With version 1.1.3 Trac changed his notification API (see [http://trac.edgewall.org/wiki/TracDev/Proposals/AdvancedNotification Advanced Notification enhancements]).

This new API should also be used in MailPlugin.

The ticket is not critical, since MailPlugin also works fine with 1.1.x (tested with 1.1.6)"	Franz
12711	SQL query problem	defect	1.2	Franz	new	2016-03-17T19:13:32+01:00	2017-11-23T17:22:51+01:00	"Hello,

Using Trac 1.1.6 with mailplugin 0.4.3
Plugin has been enabled in trac.ini
After several tries, trying to create a new simple report with only field ""Reporter"" and a where clause for Milestone (tried without any clause and getting the same error):

{{{
Illegal Arguments:
Illegal value for field 'whereClause'.

Further Informations:
(u'select id,reporter from ticket where milestone=""Unknown""', ProgrammingError(1064, ""You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'interval,active) VALUES ('test','username',1460908800000000,null,'reporter','mi' at line 1""))
}}}

Trying the same request in mysql works (`select id,reporter from ticket where milestone=""Unknown""`). I also tried `select id,reporter from ticket where milestone LIKE 'Unknown'`:
{{{
Illegal Arguments:
Illegal value for field 'whereClause'.

Further Informations:
(u""select id,reporter from ticket where milestone LIKE 'Unknown'"", ProgrammingError(1064, ""You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'interval,active) VALUES ('test','username',1460908800000000,null,'reporter','mi' at line 1""))
}}}

The VALUES seems incomplete, I don't know if it is the request or just the debug.
""'interval,active"" are always in the debug message.
Something is different compared to the picture in the wiki, I have an ""a"" letter near the date. Picture attached to this ticket.

Any idea / tests to do ?"	gbarrelet
13252	Xmail filter did not execute	defect	1.0	Franz	new	2017-08-01T11:47:17+02:00	2017-08-01T22:54:51+02:00	"On our Trac 1.0.1, I ran into a first issue during installation

{{{#!logtalk
2017-07-31 21:21:06,196 Trac[loader] ERROR: Skipping ""xmail = xmail"": 
Traceback (most recent call last):
  File ""/usr/lib/python2.7/site-packages/trac/loader.py"", line 68, in _load_eggs
    entry.load(require=True)
  File ""/usr/lib/python2.7/site-packages/pkg_resources.py"", line 2260, in load
    entry = __import__(self.module_name, globals(),globals(), ['__name__'])
  File ""build/bdist.linux-x86_64/egg/xmail/__init__.py"", line 2, in <module>
  File ""build/bdist.linux-x86_64/egg/xmail/XMailEMailModule.py"", line 22, in <module>
ImportError: cannot import name Locale
}}}

I followed the fix suggested by rjollos on comment:2:ticket:12580

{{{#!diff
Index: xmail/XMailEMailModule.py
===================================================================
--- xmail/XMailEMailModule.py	(révision 16721)
+++ xmail/XMailEMailModule.py	(copie de travail)
@@ -19,8 +19,9 @@
 from trac.notification import NotifyEmail
 from trac.util import translation
 from trac.util.datefmt import format_datetime
-from trac.util.translation import Locale, activate, domain_functions
+from trac.util.translation import activate, domain_functions
 from trac.web.api import ITemplateStreamFilter
+from trac.prefs.web_ui import Locale
 from xmail.XMailFilterObject import FilterObject
 from trac.core import Component, implements
 
}}}

Then everything seemed to go well, for testing I configured a first filter, checked the tickets list, activated it and set the execution for few minutes later but nothing happened even in the log. On Xmail page, `lastsuccessexe` is !void.

The date format used by Xmail `MM/DD/YY hh:mm:ss` is not the one configured for Trac (`ISO8601`) but I tested I can use both. Also I found that our DB is not at the same time zone as Trac but if it was an issue we would have been in trouble for a long time."	ntmlod
