I am trying to install casetracker_duedate on a clean Drupal 6.19 installation, not Open Atrium. I have tried on two different servers with PHP 5.2 and PHP 5.3 respectively. When I click on Create content > Case, I get this error:

Fatal error: Cannot unset string offsets in [/path/to/drupal]/sites/all/modules/date/date/date_elements.inc on line 273

I have tried to install Drupal several times with at most the following contrib modules:

  • casetracker
  • views
  • casetracker_duedate-6.x-1.0-alpha1
  • cck
  • date
  • features
  • litecal from github mentioned at the project page for casetracker_duedate
  • atrium_features also from github

I also tried without the github modules. Are they really required for non-Open Atrium installations? According to the installation instructions on the project page, litecal should replace the "existing" folder in /profiles/openatrium/modules/custom/litecal which does not exist in a standard Drupal installation.

I also tried to create some cases before I enabled the casetracker_duedate for the first time. After enabling the module an extra column appears in the Case Tracker listing page which is called "Due Date" and the value for all cases is "None". There is no Due Date on the Edit page for a case, but I can edit and comment the existing cases without errors. But Create content > Case is broken as above (Cannot unset string offsets...).

Am I missing something or is this a bug? Any hints on how to install this module correctly on a standard Drupal 6 installation would be appreciated!

Disclaimer: This is the first issue I created on drupal.org, so I apologize if this is the wrong way/place to do/put it.

Comments

Anonymous’s picture

Title: Create new case broken for standard Drupal install? » Create new case broken for standard Drupal install - string offset error

Thanks for reporting this!

I suspect it is related to this issue: #893118: MySql errors & missing content types in Open Atrium beta8 install

But that is mostly a guess as I haven't had a chance to investigate the problem. I will get around to fixing up this module either tomorrow or sometime the week after next. Sorry for the problems you've encountered.

But really, reporting bugs like this is a great way to start contributing to the Drupal community.

To answer your questions, no you don't need litecal or the github modules if you're on a standard drupal install. I'll make sure to fix that in INSTALL file.

Anonymous’s picture

Status: Active » Fixed

Bulk of this issue should be resolved now that #893118: MySql errors & missing content types in Open Atrium beta8 install is closed.

This should solve the readme issue. http://drupal.org/cvs?commit=430732

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

jvieille’s picture

Status: Closed (fixed) » Active

Not yet solved apparently
When trying to edit the casetracker_basic_case content type, i immediately get the error
Fatal error: Cannot unset string offsets in .../sites/all/modules/date/date/date_elements.inc on line 273

Fortunately, I still can sometime access to the "Manage fields" tab for the content type. When editing the Due Date cck field, I get the error
Fatal error: Cannot unset string offsets in .../sites/all/modules/cck/includes/content.node_form.inc on line 60

If I remove the Due Date field, the case content type goes life again.

I tried the last dev, uninstalling DD and Features, then reinstalling Feature and DD without success.
I also updated CaseTrcker to the last dev, even worse:

Thanks

Note: I don't use Open Atrium, only Case Tracker