Home
Add Issue
List Issues
Complete List
LoginList Issues
Creation date |
Sections | From | Urgency | Type |
An error occured when I tried to... chek pop3 messages
--------------------------------------------------
Error type: NameError
Error value: global name 'v' is not defined
Traceback (innermost last):
Module ZPublisher.Publish, line 115, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 41, in call_object
Module Products.IssueTrackerProduct.IssueTracker, line 8742, in check4MailIssues
Module Products.IssueTrackerProduct.IssueTracker, line 9422, in getPOP3Messages
NameError: global name 'v' is not defined
3 days old
/ignore this issue, the error was my fault in the pop3 account setup
#0742 acl
An error occured when I tried to...
--------------------------------------------------
Error type: NoACLAdderError
Error value: No ACL user object found
<p>Traceback (innermost last):
<ul>
<li> Module ZPublisher.Publish, line 115, in publish</li>
<li> Module ZPublisher.mapply, line 88, in mapply</li>
<li> Module ZPublisher.Publish, line 41, in call_object</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3579, in SubmitIssue</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3726, in createIssueObject</li>
</ul>NoACLAdderError: No ACL user object found
</p>
6 days old
I have created instance of this product in zope not in plone
#0740 Error after updating
An error occured when I tried to...
I just updated to the newest ITP (from 0.7.3 to newest), and when clicking on Complete List, I got this error:
--------------------------------------------------
Error type: UnicodeDecodeError
Error value: ascii codec can't decode byte 0xe5 in position 6: ordinal not in range(128)
<p>Traceback (innermost last): <ul>
<li> Module ZPublisher.Publish, line 114, in publish</li>
<li> Module ZPublisher.mapply, line 88, in mapply</li>
<li> Module ZPublisher.Publish, line 40, in call_object</li>
<li> Module Shared.DC.Scripts.Bindings, line 311, in __call__</li>
<li> Module Shared.DC.Scripts.Bindings, line 348, in _bindAndExec</li>
<li> Module Products.PageTemplates.PageTemplateFile, line 110, in _exec</li>
<li> Module Products.PageTemplates.PageTemplate, line 104, in pt_render<br /> <b><PageTemplateFile at /weatherTracker/CompleteList></b></li>
<li> Module TAL.TALInterpreter, line 206, in __call__</li>
<li> Module TAL.TALInterpreter, line 250, in interpret</li>
<li> Module TAL.TALInterpreter, line 711, in do_useMacro</li>
<li> Module TAL.TALInterpreter, line 250, in interpret</li>
<li> Module TAL.TALInterpreter, line 426, in do_optTag_tal</li>
<li> Module TAL.TALInterpreter, line 411, in do_optTag</li>
<li> Module TAL.TALInterpreter, line 406, in no_tag</li>
<li> Module TAL.TALInterpreter, line 250, in interpret</li>
<li> Module TAL.TALInterpreter, line 734, in do_defineSlot</li>
<li> Module TAL.TALInterpreter, line 250, in interpret</li>
<li> Module TAL.TALInterpreter, line 424, in do_optTag_tal</li>
<li> Module TAL.TALInterpreter, line 406, in no_tag</li>
<li> Module TAL.TALInterpreter, line 250, in interpret</li>
<li> Module TAL.TALInterpreter, line 653, in do_loop_tal</li>
<li> Module TAL.TALInterpreter, line 250, in interpret</li>
<li> Module TAL.TALInterpreter, line 677, in do_condition</li>
<li> Module TAL.TALInterpreter, line 250, in interpret</li>
<li> Module TAL.TALInterpreter, line 609, in do_insertStructure_tal</li>
<li> Module Products.PageTemplates.TALES, line 221, in evaluate<br />
<b>URL: CompleteList</b><br />
<b>Line 52, Column 0</b><br />
<b>Expression: standard:issue/ShowIssueThreads</b><br />
<b>Names:</b><pre>{'container': <IssueTracker at /weatherTracker>,
'context': <IssueTracker at /weatherTracker>,
'default': <Products.PageTemplates.TALES.Default instance at 0xb7468eac>,
'here': <IssueTracker at /weatherTracker>,
'loop': <Products.PageTemplates.TALES.SafeMapping object at 0x913170c>,
'modules': <Products.PageTemplates.ZRPythonExpr._SecureModuleImporter instance at 0xb73ebe0c>,
'nothing': None,
'options': {'args': ()},
'repeat': <Products.PageTemplates.TALES.SafeMapping object at 0x913170c>,
'request': <HTTPRequest, URL=http://192.168.100.1:8080/weatherTracker/CompleteList>;,
'root': <Application at >,
'template': <PageTemplateFile at /weatherTracker/CompleteList>,
'traverse_subpath': [],
'user': stine}</pre></li>
<li> Module Products.PageTemplates.Expressions, line 185, in __call__</li>
<li> Module Products.PageTemplates.Expressions, line 180, in _eval</li>
<li> Module Products.PageTemplates.Expressions, line 77, in render</li>
<li> Module Products.PageTemplates.ZRPythonExpr, line 76, in call_with_ns</li>
<li> Module Shared.DC.Scripts.Bindings, line 325, in __render_with_namespace__</li>
<li> Module Shared.DC.Scripts.Bindings, line 348, in _bindAndExec</li>
<li> Module Products.PageTemplates.PageTemplateFile, line 110, in _exec</li>
<li> Module Products.PageTemplates.PageTemplate, line 105, in pt_render<br /> <b><PageTemplateFile at /weatherTracker/001/ShowIssueThreads></b></li>
<li> Module StringIO, line 203, in getvalue</li>
</ul>UnicodeDecodeError: ascii codec can't decode byte 0xe5 in position 6: ordinal not in range(128)
</p>
12 days old
Perhaps it's because of the duplication check.
Try it on a large on like the Demo issuetracker.
2 weeks and 5 days old
To reproduce, click on Add Issue and when it's been added it doesn't show the announcement any more.
2 weeks and 5 days old
It worked here on the Real issuetracker :(
#0736 Help for this
An error occured when I tried to...
--------------------------------------------------
Error type: BadRequest
Error value: The id "acl_users" is invalid - it is already in use.
Traceback (innermost last):
Module ZPublisher.Publish, line 115, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 41, in call_object
Module Products.IssueTrackerProduct.IssueUserFolder, line 39, in manage_addIssueUserFolder
Module OFS.ObjectManager, line 297, in _setObject
Module OFS.ObjectManager, line 94, in checkValidId
BadRequest: The id "acl_users" is invalid - it is already in use.
3 weeks and 1 day old
That's really strange since it should replace an existing acl_users. Did you select any special options?
An error occured when I tried to...
--------------------------------------------------
Error type: UnicodeEncodeError
Error value: ascii codec can't encode character u'\xe9' in position 19: ordinal not in range(128)
<p>Traceback (innermost last): <ul>
<li> Module ZPublisher.Publish, line 119, in publish</li>
<li> Module ZPublisher.mapply, line 88, in mapply</li>
<li> Module ZPublisher.Publish, line 42, in call_object</li>
<li> Module Shared.DC.Scripts.Bindings, line 313, in __call__</li>
<li> Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec</li>
<li> Module Products.CheckoutableTemplates.CTFiles, line 325, in _exec</li>
<li> Module Products.PageTemplates.PageTemplateFile, line 129, in _exec</li>
<li> Module Products.PageTemplates.PageTemplate, line 89, in pt_render</li>
<li> Module zope.pagetemplate.pagetemplate, line 117, in pt_render</li>
<li> Module zope.tal.talinterpreter, line 271, in __call__</li>
<li> Module zope.tal.talinterpreter, line 346, in interpret</li>
<li> Module zope.tal.talinterpreter, line 891, in do_useMacro</li>
<li> Module zope.tal.talinterpreter, line 346, in interpret</li>
<li> Module zope.tal.talinterpreter, line 536, in do_optTag_tal</li>
<li> Module zope.tal.talinterpreter, line 521, in do_optTag</li>
<li> Module zope.tal.talinterpreter, line 516, in no_tag</li>
<li> Module zope.tal.talinterpreter, line 346, in interpret</li>
<li> Module zope.tal.talinterpreter, line 949, in do_defineSlot</li>
<li> Module zope.tal.talinterpreter, line 346, in interpret</li>
<li> Module zope.tal.talinterpreter, line 855, in do_condition</li>
<li> Module zope.tal.talinterpreter, line 346, in interpret</li>
<li> Module zope.tal.talinterpreter, line 536, in do_optTag_tal</li>
<li> Module zope.tal.talinterpreter, line 521, in do_optTag</li>
<li> Module zope.tal.talinterpreter, line 516, in no_tag</li>
<li> Module zope.tal.talinterpreter, line 346, in interpret</li>
<li> Module zope.tal.talinterpreter, line 824, in do_loop_tal</li>
<li> Module zope.tal.talinterpreter, line 346, in interpret</li>
<li> Module zope.tal.talinterpreter, line 586, in do_setLocal_tal</li>
<li> Module zope.tales.tales, line 696, in evaluate<br />
<b>URL: Statistics</b><br />
<b>Line 81, Column 8</b><br />
<b>Expression: <PythonExpr url_quote_plus(section)></b><br />
<b>Names:</b><pre>{'container': <IssueTracker at /1>,
'context': <IssueTracker at /1>,
'default': <object object at 0x0070A528>,
'here': <IssueTracker at /1>,
'loop': {'sectioncount': <Products.PageTemplates.Expressions.PathIterator object at 0x0390BB30>},
'nothing': None,
'options': {'args': ()},
'repeat': <Products.PageTemplates.Expressions.SafeMapping object at 0x01BF73F0>,
'request': <HTTPRequest, URL=http://sinfdwp01:8080/1/Statistics>;,
'root': <Application at >,
'template': <CTPageTemplateFile at /1/Statistics>,
'user': <IssueUser bonvin>}</pre></li>
<li> Module Products.PageTemplates.ZRPythonExpr, line 49, in __call__<br /> __traceback_info__: url_quote_plus(section)</li>
<li> Module PythonExpr, line 1, in <expression></li>
<li> Module DocumentTemplate.DT_Var, line 344, in url_quote_plus</li>
</ul>UnicodeEncodeError: ascii codec can't encode character u'\xe9' in position 19: ordinal not in range(128)
</p>
3 weeks and 4 days old
I think it's because you're running an old copy before the appropriate unicode features were fully added. Go to the management tab inside the issuetracker e.g. http://localhost:8080/tracker/manage_ManagementForm and click the Update Everything button. See if that helps.
i did an update everything but the error is still present. for info we use accentuated caracters is it the problem..
Hmm... That's odd then. Where do you have accentuated characters? In the status names or just in the issues?
This has been solved now and checked into trunk. I can't guarantee that your error was the same as the one I managed to reproduce and then fix but I think it was. I've checked it into the trunk so if you could please try that and let me know if it solved the problem. I had to really dig deep into the bowls of Zope to fix this problem.
Hello,
i had an accent in a section name, after removing it, the problem is solved
Thanks for your help
You shouldn't have to remove the accent in the section name. Unless of course you can't upgrade to the latest version. Thanks for your bug report anyway.
I am currently evaluating this product. I liked all the features and the interface.
I need issues to be created using email. We are using exchange server which is IMAP enabled but POP is not enabled. I am wondering whether issue tracker supports IMAP accounts instead of POP accounts. I could not find anything regarding this in the documentation.
If it is possible, could any one guide me in setting up IMAP account and get issues created automatically?
Thanks,
Anuradha
4 weeks and 1 day old
Short answer, IMAP is not supported. Sorry. I don't know how to make it look like POP3 but maybe it's possible.
Thanks for the resposnse Peter.
I will check out whether it is possible to enable POP3 in exchange server.
#0730 Bug in issue tracker
I created an issue and assigned it to myself. Later I tried to assign it to a different person and I got the attached error message. This is what I did.
1) Clicked on the issue
2) Clicked on the "change details" button
3) Selected a person from the drop down list of the "Assigned to" field.
4) Got the error message
Please let me know if you need additional information.
Thanks,
Cynthia
The error messages says that there is no MailHost to send the email to the new assignee. You need to create on and point it to your correct SMTP server. Thanks anyway.
Hi Peter,
I have configured the MailHost, but found another interesting thing...re-assigning a task (and enabling email notification) seems to work in Firefox, but not in IE. In IE, I get the following error after selecting a different user:
--------
Page Not Found, 404
/changeAssignment
Oops! Page can not be found.
Please double check the web address or use the search function on this page to find what you are looking for.
If you know you have the correct web address but are encountering an error, please send a email to the administrator of this site.
Perhaps it was one of these pages you were after:
----------
Any help appreciated...we love this product and want to continue rolling it out to our other developers!
Mike
#0729 "Strange" behavior
Hi,
It seems like when one adds 2 issues with the same details (subject, description, etc...), not necessarily one after the other, the second issue doesn't really get added. Instead, the "Issue added!" message points to the first issue. Is this a feature to prevent users from adding the same issue several times, or is this a bug?
Thank you/
1 month and 9 days old
It's deliberately so. The reason it was built this way was to prevent two issues being accidentally added when people doubleclick the "Save" button. There's no way to prevent this other than to educate your users.
By the way, there is an option to prevent people from repeating the title of the issues. This can be helpful if you want to enforce peers in your team to enter descriptive titles with the issues. I added that feature once because we were having lots of trouble to do support when people kept adding issues with the title "CMS bug" all the time with only different description.
I understand your point about users hitting "Save" twice or more. BTW there are some nice javascript options available which grey out the button after it's pressed once. But of course not everybody has javascript enabled, in which case a backup server-side solution is still needed. In my opinion, having both the javascript and the server-side logic would be best.
Anyway, I'm seeing some cases in my company where it might be needed to allow posts with the same name/description (But different users/timestamp/files). What would be very cool, and this is my feature request of the day, is to give admins a choice to enable/disable this feature!
Thanks.
Mmh I'm realizing my feature request might not be very clear. It would be a check box in the admin section, which controls if the "anti-doubleclick" logic should be enabled or disabled.
One more message, sorry about that flood (but better than no feedback at all?).
In fact, it would be very nice if the anti-doubleclick logic was looking into ALL fields of the ticket, not just the name/description, to really decide if it's the same ticket. I'm thinking, user, categories, files (check MD5 sums), etc...
I'll look into make the anti-duplication check all fields rather than just title+description. I don't think I'll have the time to add your feature request. In fact you can probably hack it yourself.
It already checks title, description, sections, type, urgency and (if applicable) email message ID.
Ok thanks, that's good to know. An MD5 hash comparison would be real cool as well, but don't worry if you don't have the time!
If the spellcorrector module is installed I think we should be able to support spellcorrection in searches.
Note-to-self: SL project will have some code that works well.
1 month and 10 days old
An error occurred when I tried to...
--------------------------------------------------
Error type: error
Error value: (10053, 'Software caused connection abort')
<p>Traceback (innermost last):
<ul>
<li> Module ZPublisher.Publish, line 119, in publish</li>
<li> Module ZPublisher.mapply, line 88, in mapply</li>
<li> Module ZPublisher.Publish, line 42, in call_object</li>
<li> Module Products.IssueTrackerProduct.Issue, line 2403, in changeAssignment</li>
<li> Module Products.IssueTrackerProduct.Issue, line 2492, in createAssignment</li>
<li> Module Products.IssueTrackerProduct.Issue, line 2558, in _sendAssignementEmail</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 6616, in sendEmail</li>
<li> Module Products.MailHost.MailHost, line 161, in _send</li>
<li> Module smtplib, line 244, in __init__</li>
<li> Module smtplib, line 310, in connect</li>
</ul>error: (10053, 'Software caused connection abort')
</p>
1 month and 11 days old
An error occured when I tried to... add a ticket to a new instance of the IssueTracker
--------------------------------------------------
Error type: error
Error value: (49, "Can't assign requested address")
Traceback (innermost last):
Module ZPublisher.Publish, line 114, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 40, in call_object
Module Products.IssueTrackerProduct.IssueTracker, line 3510, in SubmitIssue
Module Products.IssueTrackerProduct.Issue, line 2492, in createAssignment
Module Products.IssueTrackerProduct.Issue, line 2558, in _sendAssignementEmail
Module Products.IssueTrackerProduct.IssueTracker, line 6616, in sendEmail
Module Products.MailHost.MailHost, line 161, in _send
Module smtplib, line 240, in __init__
Module smtplib, line 302, in connect
error: (49, "Can't assign requested address")
~~~~~
~~~~~
~~~~~
Below are the contents of the log file:
~~~~~
~~~~~
~~~~~
Bug Reporting File
2008/03/31 15:40:01.661 GMT-4
Error type: error
Error value: (49, "Can't assign requested address")
Traceback (innermost last):
Module ZPublisher.Publish, line 114, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 40, in call_object
Module Products.IssueTrackerProduct.IssueTracker, line 3510, in SubmitIssue
Module Products.IssueTrackerProduct.Issue, line 2492, in createAssignment
Module Products.IssueTrackerProduct.Issue, line 2558, in _sendAssignementEmail
Module Products.IssueTrackerProduct.IssueTracker, line 6616, in sendEmail
Module Products.MailHost.MailHost, line 161, in _send
Module smtplib, line 240, in __init__
Module smtplib, line 302, in connect
error: (49, "Can't assign requested address")
IssueTrackerProduct version: 0.8.3
Zope: (Zope 2.8.7-DarwinPorts, python 2.3.6, darwin)
Python: 2.3.6 (#0001, Feb 7 2007, 15:35:33)
[GCC 4.0.1 (Apple Computer, Inc. build 5367)]
Platform: darwin
1 month and 13 days old
Feel free to contact me at marc @ nextnewnetworks.com
I'm sorry but there's nothing the IssueTrackerProduct can do to help you there. Basically, you're trying to send emails via an SMTP server that you're not able to connect to. Whichever server the issuetracker is installed on, check with ping or some other means if you can connect to whatever server you've configured in the MailHost object in Zope.
I've installed and setup the Issue Tracker Product and have been able to get everything working except when i add an issue i never get an email notification. I've added my email to the global notifyables and the local notifyables for the Issuetracker instance. I'm using a locally installed smtp server "localhost" port 25. the tell-a-friend feature works fine and i get the email instantly.
here is some info on the software i'm running:
Debug Information
* Zope version: (Zope 2.10.5-final, python 2.4.4, win32)
* Python version: 2.4.4 (#0071, Oct 18 2006, 08:34:43) [MSC v.1310 32 bit (Intel)]
* System Platform: win32
* SOFTWARE_HOME: C:\Zope\2.10.5\Zope\lib\python
* INSTANCE_HOME: C:\Zope\Instance\2.10.5
* CLIENT_HOME: C:\Zope\Instance\2.10.5\var
* Process ID: 2848 (2296)
* Running for: 29 min 42 sec
* sys.path:
C:\Zope\Instance\2.10.5\lib\python
C:\Zope\Instance\2.10.5\lib\python
C:\Zope\2.10.5\Zope\lib\python\Zope2\Startup
C:\Zope\2.10.5\Python\lib\site-packages\setuptools-0.6c7-py2.4.egg
C:\Zope\Instance\2.10.5\lib\python
C:\Zope\2.10.5\Zope\lib\python
C:\Zope\2.10.5\Zope\lib\python\third_party\docutils
C:\Zope\2.10.5\Zope\lib\python\third_party\docutils\extras
C:\Zope\2.10.5\Python\python24.zip
C:\Zope\2.10.5\Python\DLLs
C:\Zope\2.10.5\Python\lib
C:\Zope\2.10.5\Python\lib\plat-win
C:\Zope\2.10.5\Python\lib\lib-tk
C:\Zope\2.10.5\Python
C:\Zope\2.10.5\Python\lib\site-packages
C:\Zope\2.10.5\Python\lib\site-packages\win32
C:\Zope\2.10.5\Python\lib\site-packages\win32\lib
C:\Zope\2.10.5\Python\lib\site-packages\Pythonwin
1 month and 13 days old
Sadly that stuff about "notifyables" is confusing. Actually, a notifyable was a feature that made it possible to refer to another user by name rather than by email. The thought was that names rarely change but email does.
What you need to do is use the Properties tab and enter your email address in the "Always notify" box. Alternatively you can enter your login username if you use IssueTracker UserFolder or if you've set up a notifyable called "diego" that points to "diego~at~emailaddress_._com".
thanks for the response, but it still does not send an email to either an email address in the Always Notify box, or a predefined username. Also I've noticed that when i use the Tell a Friend feature, the link in the email i received goes to a dead link. so far the only way we have of notifying the other techs in the office is to use the RSS feed. Any help is greatly appreciated!
Very odd. There's another option in the Properties to select if people should see who will be notified when you add new issues. Enable that and the click to add a new issue and when you're previewing, does it say which people it will notify when you submit the issue?
Thanks for your response. Yes I have set it up that way so i can see a preview and it I'm always the one its supposed to notify. the weird thing is that i've noticed on the activity log on my smtp server that when I click on "tell a friend" i see a connection from my Issuetracker server, and when i submit an issue nothing happens on the smtp server, is there a diferent version of the issue tracker software i can install and try? Can you think of any other solution? I love the software, but this email thing would make it 5 times better
First of all, why are the links dead when using the Tell-a-friend? What do they link to?
Secondly, some email work and some don't you say? I suspect it has very much to do with the from address and/or the the to address. Perhaps your SMTP server is set up to reject emails coming from issuetracker@localhost but works for email from something_at_petpev%20dot%20com. I can help you debug this but look into the above first.
An error occured when I tried to add a new issue.
I have upgraded to 0.8.3.
What Zope version do you recommend?
--------------------------------------------------
Error type: RuntimeError
Error value: maximum recursion depth exceeded in cmp
<p>Traceback (innermost last):
<ul>
<li> Module ZPublisher.Publish, line 115, in publish</li>
<li> Module ZPublisher.mapply, line 88, in mapply</li>
<li> Module ZPublisher.Publish, line 41, in call_object</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3471, in SubmitIssue</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3725, in generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 3760, in _do_generateID</li>
</ul>RuntimeError: maximum recursion depth exceeded in cmp
</p>
1 month and 2 weeks and 5 days old
I've stared at the code where this could have happened and can't for the love of me see why it would happen. What Zope version are you running?
I'd recommend zope 2.10, 2.9 or 2.8. Zope 2.9.8 I think we use a lot here for our issuetrackers.
I am running Zope version 2.9.6 but I managed to sort this out. I increased the number from 6 to 7 and resolved this.
Thanks
Mike
I am running 8.3, while I was waiting on a couple patches. I renamed IssueTrackerProduct to IssueTrackerProduct.8.3 and renamed IssueTrackerProduct.svn back to IssueTrackerProduct. Then in the ITproduct folder, I ran svn update. The, I chowned (-r) the directory to the correct user:group. But when I start zope with this folder in place I get the following error message.
This object is broken because the IssueTrackerProduct product that created it is no longer installed or is installed incorrectly. Please contact the product maintainer for assistance.
Note that the data associated with this product has not been lost, and will be accessible again if the product is reinstalled.
and from the root view, my ITproduct instance has a broken icon with a "?" on it saying: helpdesk (This object from the IssueTrackerProduct product is broken!)
I successfully reverted to the 8.3 with no problems. But I wonder if I did an svn update at the wrong time?
1 month and 2 weeks and 5 days old
If it's broken you should get some errors in the event log if the product (from svn) can't be installed. It's important that the name is "IssueTrackerProduct" no matter where it comes from (SVN or .tgz). Any other name with break it.
Look for errors and deal with those. It could be permission related if you've got a complex setup.
If you don't get any errors in the event.log, try clicking on IssueTrackerProduct in /Control_Panel/Products/manage_main
I tried a fresh svn checkout on a dev system with the same specs. This is what the event log says.
2008-04-14T01:09:09 ERROR Application Could not import Products.IssueTrackerProduct
Traceback (most recent call last):
File "/usr/lib/zope2.10/lib/python/OFS/Application.py", line 703, in import_product
product=__import__(pname, global_dict, global_dict, silly)
File "/var/lib/zope2.10/instance/sandbox/Products/IssueTrackerProduct/__init__.py", line 13, in ?
import IssueTracker
File "/var/lib/zope2.10/instance/sandbox/Products/IssueTrackerProduct/IssueTracker.py", line 133, in ?
from TemplateAdder import addTemplates2Class, CTP
File "/var/lib/zope2.10/instance/sandbox/Products/IssueTrackerProduct/TemplateAdder.py", line 123, in ?
from Constants import DISABLE_CHECKOUTABLE_TEMPLATES
File "/var/lib/zope2.10/instance/sandbox/Products/IssueTrackerProduct/Constants.py", line 222
'sxi':'sxi.png', 'sxw':'sxw.png' 'rar':'rar.png',
^
SyntaxError: invalid syntax
------
2008-04-14T01:09:10 WARNING OFS.Uninstalled Could not import class 'IssueTracker' from module 'Products.IssueTrackerProduct.IssueTracker'
------
2008-04-14T01:09:13 ERROR Application Couldn't install IssueTrackerProduct
Traceback (most recent call last):
File "/usr/lib/zope2.10/lib/python/OFS/Application.py", line 752, in install_product
global_dict, global_dict, silly)
File "/var/lib/zope2.10/instance/sandbox/Products/IssueTrackerProduct/__init__.py", line 13, in ?
import IssueTracker
File "/var/lib/zope2.10/instance/sandbox/Products/IssueTrackerProduct/IssueTracker.py", line 133, in ?
from TemplateAdder import addTemplates2Class, CTP
File "/var/lib/zope2.10/instance/sandbox/Products/IssueTrackerProduct/TemplateAdder.py", line 123, in ?
from Constants import DISABLE_CHECKOUTABLE_TEMPLATES
File "/var/lib/zope2.10/instance/sandbox/Products/IssueTrackerProduct/Constants.py", line 222
'sxi':'sxi.png', 'sxw':'sxw.png' 'rar':'rar.png',
^
SyntaxError: invalid syntax
------
2008-04-14T01:09:13 INFO Zope Ready to handle requests
I know the date is off, that is a separate issue, but the 8.3 tar file works and is the same
Here are the system settings.
Zope Version
(Zope 2.10.3-final, python 2.4.4, linux2)
Python Version
2.4.4 (#0002, Mar 7 2008, 04:45:43) [GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)]
System Platform
linux2
SOFTWARE_HOME
/usr/lib/zope2.10/lib/python
ZOPE_HOME
/usr/lib/zope2.10
INSTANCE_HOME
/var/lib/zope2.10/instance/sandbox
CLIENT_HOME
/var/lib/zope2.10/instance/sandbox/var
Network Services
ZServer.HTTPServer.zhttp_server (Port: 8028)
Process Id
2926 (-1262044272)
Argh!! It was an accident. I managed to check in a python file that had a Syntax error in it. :( Just do a SVN update and try again. I really ought to combine the checkins with running of unit tests.
Updated to build 198, but the menu is broken. Notice the copy and paste of the menu below, there is a duplicate for each menu item overlapping it.
* Home Home
* Add Issue Add Issue
* Quick Add Issue Quick Add Issue
* List Issues List Issues
* Complete List Complete List
* User admin
Also attached is a screenshot.
On the bright side, pop3 retrieval did work. Though it is not formatting the html emails from outlook properly.
Look for any errors in the event log. There's something wrong, perhaps, about how images are installed.
Hi Peter,
I can see that in your Demo Issuetracker there is to thing that i don't have in the latest version from the download :
1. You get an small thumbnail if there is a picture as an attachement. I don't get that.
2. You have that Click gere to attach one or more files
Mihai
1 month and 2 weeks and 5 days old
- You need to have the python library PIL installed.
- In the last SVN version soon to be released.
I am not sure how the issuetracker emails are parsed so that an email can be identified as either a new ticket or a followup on an existing one.
I see the ticket ID in the subject of sent messages. Myself and others frequently reply to tickets via email for a quick response, then follow up with more detail on the website. I usually delete the contents of the previous email when I reply to a ticket, so there isn't a ton of duplication. I usually instruct the client to do the same, so the threads aren't crazy long. Most of our clients create and respond to tickets via email, so this is kind of critical for us.
But when I send an email with only the subject containing the ticket ID it sees it as a new ticket, so it is not using the subject to determine if it is new or a reply.
Is there a way to make the parser identify the subject with the ticket id format? Or is there something we can specify in the body, so that we can instruct the users to include it in the replies. Most other mail enabled helpdesk systems only need to see something like "Ticket ID:xxx" in the subject to know it is an update not a new ticket. Ideally, it would be really helpful if a user could reply to a send to a friend email notification to reply.
1 month and 3 weeks and 1 day old
It's been a while since I worked on this. Allow me to explain how it distinguished between replies and new emails. Match on any of these:
- The header ID and if it refers to an existing issue.
- The URL of the issuetracker somewhere in the body. If so...
- It looks for a mentioned issue number that exists
That's the primary tests. Then it gets more detailed. If any of these match, it's a reply rather than a new issue:
- The configured signature is in the body
- It says "<Name of Tracker>: new issue" somewhere in the subject line
- It says "<Name of Tracker>" in the subject line and ...:
- It also matches a mentioned Issue Id and/or Title in the subject line
- The body contains the line "Thank you for submitting this issue via email." (this is my least favorite)
Basically, there's no immediate way to "fake" a non-reply into appearing as a issue followup. The best solution for you would be to write a monkey patch or something like that to extend this functionality. Sadly the function is quite big that does these checks and it's private so you'd have to get your best editor out to do it.
#0720 unauthorized user
An error occured when I tried to...
-------------------------------------------------- Error type: Unauthorized Error value: <strong>You are not authorized to access this resource.</strong>
<p>Traceback (innermost last): <ul>
<li> Module ZPublisher.Publish, line 105, in publish</li>
<li> Module ZPublisher.BaseRequest, line 461, in traverse</li>
<li> Module ZPublisher.HTTPResponse, line 686, in unauthorized</li>
</ul>Unauthorized: <strong>You are not authorized to access this resource.</strong> </p>
1 month and 3 weeks and 3 days old
I can't get the mail to work at all. I have an SMTP server without authentication (i have also tried with authentication). I have tried MailHost and SecureMailHost.
I get this error in the event log :
2008-03-19T10:00:36 WARNING IssueTrackerIssue Message could not be sent
Traceback (most recent call last):
File "C:\Zope\Instance\2.10.5\Products\IssueTrackerProduct\Issue.py", line 2305, in TellAFriend
self.sendEmail(msg, both, fr, subject, swallowerrors=False)
File "C:\Zope\Instance\2.10.5\Products\IssueTrackerProduct\IssueTracker.py", line 6616, in sendEmail
mailhost._send(fr, to, message.as_string())
AttributeError: _send
1 month and 3 weeks and 4 days old
Do you have a SecureMailHost or a normal MailHost?
Sorry, just now saw that you wrote "I have tried MailHost and SecureMailHost."