Posted by lblake on June 13, 2009 at 3:47pm
Jump to:
| Project: | Case Tracker |
| Version: | 6.x-1.0-beta4 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I receive the following trying to access Casetracker:
warning: array_fill() [function.array-fill]: Number of elements must be positive in /var/www/includes/database.inc on line 241.
warning: implode() [function.implode]: Bad arguments. in /var/www/includes/database.inc on line 241.
And two "user warning: You have an error in your SQL syntax" errors. I have tried installing 6.x-1.0-beta1 and 6.x-1.x-dev
Drupal 6.12 MySQL 5.0.51a PHP 5.2.4
Thanks for any assistance.
Comments
#1
I need a bit more info to help here. Where exactly, what URL, are you are getting these errors? Which case tracker modules to you have enabled? Can you provide steps by which I could reproduce this issue?
Thanks.
#2
I can reproduce this with drupal-6.14 and casetracker-6.x-1.0-beta4 (mysql-5.1.40, php-5.2.10, but I think this doesn't matter).
When I try to access
?q=casetracker, I get those pesky warnings, and the view doesn't list any cases. (I thought I get those because I didn't have any cases, but I can't see anything in the view even after adding a case.) I have enabled only thecasetracker.module, but I'm havingog.module,og_access.moduleandog_views.moduleenabled (to have project-based access rules), but I don't know if this is related.Steps I have taken: install the above-mentioned modules, add some project nodes (casetracker projects, og groups; private and closed groups), go to one of the CT-provided views (
?q=casetrackeror?q=casetracker/my), and voilá: pesky red warnings arise, without any useful content. I'm setting this as critical as this renders CT unusable for me.#3
Disabling all of OG-related modules
og.module,og_access.moduleandog_views.moduledoesn't resolve this issue.Anyway it seems I have found the root of all evil: I have not enabled any content types as case node type at
?q=admin/settings/casetracker. Ticking at least one of the content types as case node type (and saving the form, of course) resolves this issue (thus I'm setting it back to normal). Anyway, it would be great if this user error (?) could be handled in a way that's a bit more user friendly (thus why I'm leaving it active).#4
@Boobaa, thank you for tracking this down. I've just committed a fix http://drupal.org/cvs?commit=327874
#5
Automatically closed -- issue fixed for 2 weeks with no activity.