Posted by rar on October 24, 2007 at 4:19pm
Jump to:
| Project: | Timer |
| Version: | 5.x-1.0 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | John Money |
| Status: | active |
Issue Summary
1) Add module "Case tracker: basic"
2) Add module "Timer"
3) Add Timer field ( /admin/content/types/casetracker-basic-case/add_field )
4) Create content ( /node/add/casetracker-basic-case )
5) Get Sementation faults from Apache when you try to view, edit, or delete the page. Can only delete the node by going into the database directly and deleting it there.
I haven't tested this yet with other non-casetracker content-types.
Comments
#1
Thank you for the bug report.
I had not tested Timer with Case Tracker. Something is obviously not playing well, though I have used Timer in other custom CCK-type nodes without issue. I will investigate further.
#2
I am having a very similar, and probably related issue. While I have Casetracker installed, I am not adding the timer to a Casetracker content type. Instead I created a new content type and added the Timer field to it. I am finding the same behaviour - the node I created with this new content type will not display, instead crashing Drupal. I can not delete the node using the Admin interface, and will have to delete directly from the database.
#3
I am in the process of moving my site to a new server, after which I will finally (hopefully) get to the bottom of why Timer and Casetracker don't play well together.
#4
subscribing
#5
+1 subscribing
#6
Subscribing; I also get this problem
#7
subscribing