Thanks for providing this really useful module, it's worked great up until just recently.

I'm an Open Atrium user who uses Time Tracker with Case Tracker. Recently OA updated to v. 1-0 beta 8, which also included an update to Drupal 6.19 and Case Tracker 6.x-1.0 beta 8.

When I try to add a comment to a case, I receive the following error: Fatal error: Cannot use string offset as an array in \includes\form.inc on line 990, and, of course, the comment fails. If I disable Time Tracker, I'm able to post comments on cases.

I really get a lot of use out of this module and hope this is something that is easily fixable.

Comments

codi’s picture

codi commented
Assigned: Unassigned » codi

Hey fenns, sorry about the delay on this one. I was away on holidays. Just upgrading my test site to the new atrium beta and i'll take a look.

mattconnolly’s picture

mattconnolly commented

I just found this exact problem with a custom module I'm writing now. The problem is in the function that is called by drupal_get_form to generate the form.

If it starts like this:

function my_custom_form($form, $form_state)
{
  // setup $form here....
  return $form;
}

That's where your problem is. There's no $form in the form constructor, that only happens in the validate and submit functions. The constructor should just be:

function my_custom_form($form_state)
{
  $form = array(....);
  return $form;
}

good luck,
Matt.

evillage.pl’s picture

evillage.pl commented

When I try to add a new comment to a case

Cannot use string offset as an array in (...)/sites/all/modules/custom/seed/seed.module on line 324

codi’s picture

codi commented

Can you guys confirm that these problems are still happening with the latest dev commits. We've been adding some features and smoothing out others the last couple of days.

drclaw’s picture

drclaw commented
Status: Active » Closed (fixed)

This issue has been fixed. Try latest dev release.

dgtlmoon’s picture

dgtlmoon commented

Yeah recheck your function definition for your hook_form, it's easy to put in the wrong parameter definition which can cause funky errors like the above