MySql errors & missing content types in Open Atrium beta8 install

I can confirm this same behavior. Interestingly, even though the case tracker content types disappear from the admin content type menu, all the case tracker content is still there in all my groups. They don't have the due date field, but they didn't disappear with the loss of the content type.

I edited the .info file for the case tracker due date feature to not require the case_tracker_basic module and the content types don't disappear. However, as soon as I enable the casetracker_basic module they disappear. When I disable it again, they come back. I know this isn't much insight, but I just wanted to share as I try and dig into the issue.

I'm not fully sure of how the atrium_casetracker, casetracker, and casetracker_basic module relate.

I've been able to get it 90% working, by disabling parts of the functions in the install of the module. It's weird. When it boils down to it "I think" it has something to do with the alter to the calendar view. The alter seems to need it's own argument for the due date type, rather than having the due date type being included in the argument for the event types. Getting close to a patch...

Patch

OK here's a patch that worked for me to fix the problem. Please review and test it out on your install. Just to be clear, I am using this on Open Atrium specifically. I'm not entirely sure if people are using this without Open Atrium...maybe I'm assuming too much there.

What I did:

• removed the casetracker_basic module depenency
• modified the alters to the calendar view
• setup the due_date field as its own argument
• added a filter that prevents cases from showing up on the calendar if there is no due date assigned

Upgrade path

What I did to test

1. Created a dev version of my Open Atrium site (pre beta 8)
2. Replaced my old Open Atrium code with the new Open Atrium beta 8 code
3. Clear all caches
4. Followed the upgrade instructions here and then here. AKA - upgrade the db, and reset your features.
5. Clear all caches
6. Enable the casetracker_duedate module (with this patch obviously)
7. Seems like things work. I can see all the content types, no MySQL errors, and I can add due dates to cases, causing them to show up in the calendar and upcoming views.

Whitespace

When I made the patch I told the diff to ignore the whitespace. There are lots of stray whitespace endings in the module file. It'd be good to clean those out, but I didn't want to confuse this patch with that extra stuff.

Hope this works for others as well.

Hello,

I tried the patch and it works. But I have another problem: I have entered a task with dates from 01.07.2010 to 31.07.2010. But in the calendar the case is shown form 30.06.2010 to 30.07.2010 (see attachement).

Jan

That's interesting. The case content type shouldn't have a from and to due date. It just has a single date value. Right?

I think knarzer77 actually found a bug in this patch. I've got the granularity for the due date field settings including the hours, min, and sec. The default format in the view is also wrong. So I'm working on a 2nd patch that I'll upload here in a little bit.

Patch in #6 re-rolled so it applies cleanly for contrib (and can be included in a make file).

I don't see where a to date is part of the casetracker_duedate functionality referenced in #7. I only see a single date field.

It seems that some versions of drush don't like patch files with spaces in them. sorry for so many posts in here with essentially the same patch.

just to clear up all I did was re-roll so that the file paths in the patch were correct.