Closed (won't fix)
Project:
Case Tracker
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 May 2009 at 21:53 UTC
Updated:
28 Apr 2010 at 00:30 UTC
I've got bug tracking running nicely in this beta with a few users and two projects without fault.
Today I tried configuring CT Mail with mailhandler with a grievous waste of time connecting to the IMAP server (grrrr...)
When I reply to an email sent by Case tracker and run cron.php, the next view of the relevant case shows the following errors:
warning: array_keys() [function.array-keys]: The first argument should be an array in /home/airdream/public_html/sites/projects.brightonart.eu/modules/casetracker/casetracker_mail.module on line 202.
warning: array_shift() [function.array-shift]: The argument should be an array in /home/airdream/public_html/sites/projects.brightonart.eu/modules/casetracker/casetracker_mail.module on line 205.
warning: array_keys() [function.array-keys]: The first argument should be an array in /home/airdream/public_html/sites/projects.brightonart.eu/modules/casetracker/casetracker_mail.module on line 202.
warning: array_shift() [function.array-shift]: The argument should be an array in /home/airdream/public_html/sites/projects.brightonart.eu/modules/casetracker/casetracker_mail.module on line 205.
warning: array_keys() [function.array-keys]: The first argument should be an array in /home/airdream/public_html/sites/projects.brightonart.eu/modules/casetracker/casetracker_mail.module on line 202.
warning: array_shift() [function.array-shift]: The argument should be an array in /home/airdream/public_html/sites/projects.brightonart.eu/modules/casetracker/casetracker_mail.module on line 205.
user warning: Table 'airdream_bartprojects.casetracker_project' doesn't exist query: SELECT nid FROM casetracker_project WHERE project_number = 0 in /home/airdream/public_html/sites/projects.brightonart.eu/modules/casetracker/casetracker_mail.module on line 211.
Comment: unauthorized comment submitted or comment submitted to a closed post Re: [Carhouse Bug 1-67] reassigned.
The post is not closed.
If no-one has a quick fix I'll try and debug this a bit next week ...
Comments
Comment #1
jmiccolis commentedI'm not using, nor have I put much work into the mail sending or receiving functionality in the DRUPAL-6 branch of casetracker. All my installs are using the messaging and notifications. So help in stabilizing / fixing CT Mail in general is *very* much appreciated. It is the one part of Case Tracker that isn't stable right now, and I'd like it to be.
Comment #2
marcus_clements commentedI really like the look of handling incoming mails and turning them into comments as that would integrate so well into our existing workflow.
I'm using messaging and notifications on another project, but is there an incoming mail handler that works with those modules? I assume not.
When I get a few moments I'll be happy to look into the errors I'm getting and post a patch.
cheers
Marcus
Comment #3
Ian Ward commentedmail2web will handle incoming emails and turn them into comments http://drupal.org/project/mail2web I have two patches that I need to post soon that enable mail2web to work well for handling incoming comments to cases from the casetracker, as well as handling outgoing messages w/ some special tokens for composing these messages w/ the messaging module. I'll try to get these posted in the next week.
Comment #4
erald commentedI have the same error when sending mail to the system.
In my database I can not find the casetracker_project table either.
any news on this problem?
Comment #5
jmiccolis commentedErald,
I'm not sure the anyone is working directly on this issue and I presume that most people are using notifications module, possibly with mail2web in place of the built in functionality.
It's looking more like we'll be deprecating this sub-module very soon.
Comment #6
Tars commentedI'm experiencing same problems:
Any ideas?
Comment #7
asak commentedI'm getting exact same errors.
Truth is i WAS using mail2web with the messaging modules, but when replying to mails i found stuff like this in the comment:
This does not seem to make a real change in the node, even though it's marked as if it does. even the change of assignment does not change the node settings.
@Ian Ward: care to share those patches? ;)
Comment #8
KrisBulman commentedIan, can you provide some insight on getting casetracker working for comment replies to casetracker tickets? (I'm using atrium)
Comment #9
KrisBulman commentedsame error when replying to tickets
also posted a new ticket in mail2web issue queue:
http://drupal.org/node/563474
Comment #10
blender1968 commented+1 via Atrium
Comment #11
jmiccolis commentedHi all,
I'm looking for feedback on how we can move forward with CT Mail, as it's the big release blocker for Drupal 6 http://drupal.org/node/712794
Comment #12
jmiccolis commentedI've just removed CT mail from the Casetracker suite. My intention is to replace it with a messaging and notifications module that extends what you can already do with those modules and mail comments. However this issue no longer applies to Case Tracker - setting it to "won't fix".