{project_issues} table not being created when module is enabled

Hi,

1) Project 5.x-1.2 and Project issue tracking 5.x-2.x-dev - (also tried latest stable release)

2) I do get an error in watchdog - not certain if it has anything to do with project.. it is;

Type php
Date Wednesday, July 16, 2008 - 13:16
User Robin
Location http://plainsightgame.com/?q=admin/logs/watchdog
Referrer http://plainsightgame.com/
Message preg_match() expects parameter 2 to be string, array given in C:\www.plainsightgame.com\includes\bootstrap.inc on line 670.
Severity error
Hostname 87.236.135.80

3) A list of my modules are below ...

4) This is a new site and my first install of Project. It can be viewed at www.plainsightgame.com

ive created a temp account - username + password: testbeta

thanks
Robin

modules
ACL 5.x-1.6
Forum Access 5.x-1.10
Action email role 5.x-2.x-dev
Actions 5.x-2.5
Administration Menu 5.x-2.5
Aggregator 5.8
Blog 5.8
Blog API 5.8
Book 5.8
Color 5.8
Comment 5.8
Forum 5.8
Help 5.8
Menu 5.8
Ping 5.8
Search 5.8
Taxonomy 5.8
Tracker 5.8
Upload 5.8
Block 5.8
Filter 5.8
Node 5.8
System 5.8
User 5.8
Watchdog 5.8
Invite 5.x-1.13
Invite Statistics 5.x-1.13
Privatemsg 5.x-1.8
Usernode 5.x-1.4
Advanced Forum 5.x-1.0-alpha10
BUEditor 5.x-1.1
Comment upload 5.x-0.1
Google Analytics 5.x-1.6
Legal 5.x-1.3
Menu Per Role 5.x-1.x-dev
Quick Tabs 5.x-1.3
Token 5.x-1.11
Video Filter 5.x-2.4
Project 5.x-1.2
Project issue tracking 5.x-2.x-dev
Project releases 5.x-1.2
Project usage 5.x-1.2
Signatures for forums 5.x-2.3
Apply for role 5.x-1.4
Role 5.x-3.0
Role exempt 5.x-3.0
User Points Top Contributors 5.x-1.0
Userpoints 5.x-3.7
Userpoints Autoapprove 5.x-3.0
Userpoints Basic 5.x-3.7
Views Integration 5.x-3.7
Views 5.x-1.6
Views RSS 5.x-1.6
Views Theme Wizard 5.x-1.6
Views UI 5.x-1.6

going to re install, start by getting project working and building the site up from there......

this appears to to be the problem. Project issues isn't creating a database table:

error is :

 * user warning: Table 'plainsight.project_issues' doesn't exist query: SELECT COUNT(DISTINCT(n.nid)) FROM node n INNER JOIN project_issues p ON p.nid = n.nid INNER JOIN node_revisions r ON r.vid = n.vid INNER JOIN users u ON p.assigned = u.uid LEFT JOIN comments c ON c.nid = p.nid LEFT JOIN comment_upload_files cu ON p.nid = cu.nid LEFT JOIN files f ON n.nid = f.nid WHERE n.status = 1 AND (((n.uid = '1') OR (p.assigned = '1') OR (c.uid = '1'))) AND ((p.sid = '1' OR p.sid = '2' OR p.sid = '4')) in C:\www.plainsightgame.com\includes\database.mysql.inc on line 172.
    * user warning: Table 'plainsight.project_issues' doesn't exist query: SELECT DISTINCT(n.nid), n.changed FROM node n INNER JOIN project_issues p ON p.nid = n.nid INNER JOIN node_revisions r ON r.vid = n.vid INNER JOIN users u ON p.assigned = u.uid LEFT JOIN comments c ON c.nid = p.nid LEFT JOIN comment_upload_files cu ON p.nid = cu.nid LEFT JOIN files f ON n.nid = f.nid WHERE n.status = 1 AND (((n.uid = '1') OR (p.assigned = '1') OR (c.uid = '1'))) AND ((p.sid = '1' OR p.sid = '2' OR p.sid = '4')) ORDER BY n.changed DESC LIMIT 0, 20 in C:\www.plainsightgame.com\includes\database.mysql.inc on line 172. 

... I can make this table manually - but what fields do i need?

thanks

Rob

PS: I've wiped the site so, obviously, previous l+p wont work ;)

i've just done a fresh install. I get this error the moment i enable Project issues module

What ive done:

1) Wipe old website directory and database table
2) Fresh install of Drupal 5.8
3) Install + enable Project module - works fine
4) Install + enable Comment Upload module - works fine
5) Enable Upload module - fine
6) Install + enable Project issues - get the error..

Checked again, there is no database table..

There is nothing else on the site.

Cheers

i get this on admin/build/modules and project/issues

that's correct :
Project Issue 2.2 (latest stable)
Project 1.2 (latest stable)

checked the database for any other errors - none found. Did yet another install, same error :

    * user warning: Table 'plainsight.project_issues' doesn't exist query: SELECT COUNT(n.nid) FROM node n INNER JOIN project_issues p ON p.nid = n.nid INNER JOIN node_revisions r ON r.vid = n.vid INNER JOIN users u ON p.assigned = u.uid WHERE n.status = 1 AND ((p.sid = '1' OR p.sid = '2' OR p.sid = '4')) in C:\www.plainsightgame.com\includes\database.mysql.inc on line 172.
    * user warning: Table 'plainsight.project_issues' doesn't exist query: SELECT n.nid FROM node n INNER JOIN project_issues p ON p.nid = n.nid INNER JOIN node_revisions r ON r.vid = n.vid INNER JOIN users u ON p.assigned = u.uid WHERE n.status = 1 AND ((p.sid = '1' OR p.sid = '2' OR p.sid = '4')) ORDER BY n.changed DESC LIMIT 0, 20 in C:\www.plainsightgame.com\includes\database.mysql.inc on line 172.

in MYSQL I used this :

CREATE TABLE project_issues (
  nid int NOT NULL default '0',
  pid int NOT NULL default '0',
  fid int NOT NULL default '0',
  category varchar(255) NOT NULL default '',
  component varchar(255) NOT NULL default '',
  priority smallint NOT NULL default '0',
  rid int NOT NULL default '0',
  assigned int NOT NULL default '0',
  state smallint NOT NULL default '0',
  PRIMARY KEY (nid)
);
CREATE INDEX project_issues_pid ON project_issues(pid);

ALTER TABLE project_issues DROP fid;
ALTER TABLE project_issues ADD file_path varchar(255);
ALTER TABLE project_issues ALTER file_path SET NOT NULL;
ALTER TABLE project_issues ALTER file_path SET default '';
ALTER TABLE project_issues ADD file_mime varchar(255);
ALTER TABLE project_issues ALTER file_mime SET default '';
ALTER TABLE project_issues ALTER file_mime SET NOT NULL;
ALTER TABLE project_issues ADD file_size int;
ALTER TABLE project_issues ALTER file_size SET default 0;
ALTER TABLE project_issues ALTER file_size SET NOT NULL;

then manually made a SID entry... seems to have solved the issue - will report back if im wrong !

cheers

i agree, the alter table commands aren't needed (just copied and pasted it from another source) .

from the .install - this works :

CREATE TABLE project_issues (
          nid int(10) unsigned NOT NULL default '0',
          pid int(10) unsigned NOT NULL default '0',
          category varchar(255) NOT NULL default '',
          component varchar(255) NOT NULL default '',
          priority tinyint(3) unsigned NOT NULL default '0',
          rid int(10) unsigned NOT NULL default '0',
          assigned int(10) unsigned NOT NULL default '0',
          sid int(10) unsigned NOT NULL default '0',
          original_issue_data text NOT NULL,
          last_comment_id int NOT NULL default 0,
          db_lock tinyint NOT NULL default 0,
          PRIMARY KEY (nid),
          KEY project_issues_pid (pid),
          KEY project_issues_sid (sid),
          KEY project_issues_nid_assigned (nid, assigned)
          );
        

and then.....

              CREATE INDEX project_issues_pid_idx ON project_issues(pid);
	      CREATE INDEX project_issues_sid_idx ON project_issues(sid);
	      CREATE INDEX project_issues_nid_assigned_idx ON project_issues(nid, assigned);

I havent tried this on 5.7 yet, will give it a crack tomorrow

What seems to be failing in the .install is this :
ERROR 1101 (42000): BLOB/TEXT column 'original_issue_data' can't have a default value

hence why i changed: original_issue_data text NOT NULL default '',
to :
original_issue_data text NOT NULL,

seems to work ... im going to give it some testing and report back (god knows what else the .install missed ;) )

im getting the error when i manually execute the mySQL statement - but, if it failed during the .install, then that could explain why there is no project_issues table

My system:
Drupal 5.8
Configuration file Protected
Cron maintenance tasks Last run 2 hours 39 min ago
You can run cron manually.
Database schema Up to date
File system Writable (private download method)
GD library bundled (2.0.34 compatible)
MySQL database 5.0.51a
PHP 5.2.5
PHP register globals Disabled
Unicode library PHP Mbstring Extension
Web server Apache/2.0.59 (Win32) PHP/5.2.5 DAV/2

you think thats it?

Also, thanks very much for all your help!

Robin

tried this on a 5.7 install -same issue !

anyway, after playing around, i found out the the same error stopped project_issues_comments being made...

so, once again, I manually ran:

CREATE TABLE project_issue_comments (
          nid int(11) default NULL,
          cid int(11) default NULL,
          rid int(11) NOT NULL default '0',
          component varchar(255) NOT NULL default '',
          category varchar(255) NOT NULL default '',
          priority int(11) NOT NULL default '0',
          assigned int(11) NOT NULL default '0',
          sid int(11) NOT NULL default '0',
          pid int(10) unsigned NOT NULL default '0',
          title varchar(255) NOT NULL,
          timestamp int(10) unsigned NOT NULL,
          original_issue_data text NOT NULL default '',
          PRIMARY KEY(cid),
          INDEX nid_timestamp (nid, timestamp)
        )

this has finally fixed the issue. Project issue tracking now works fine.

Must admit it's a very odd error - it's probably just my system however, if anyone else has this issue, hopefully they can solve it in the same way ;)

thanks again for all your help

sorry , i meant :

CREATE TABLE project_issue_comments (
          nid int(11) default NULL,
          cid int(11) default NULL,
          rid int(11) NOT NULL default '0',
          component varchar(255) NOT NULL default '',
          category varchar(255) NOT NULL default '',
          priority int(11) NOT NULL default '0',
          assigned int(11) NOT NULL default '0',
          sid int(11) NOT NULL default '0',
          pid int(10) unsigned NOT NULL default '0',
          title varchar(255) NOT NULL,
          timestamp int(10) unsigned NOT NULL,
          original_issue_data text NOT NULL,
          PRIMARY KEY(cid),
          INDEX nid_timestamp (nid, timestamp)
        );

[forgot to chop default '' ! ]

----

NOTE: Also, to stop additional errors I had to change both 'original_issue_data' fields to VARCHAR - this is because the TEXT type can't have the Default entry at a length of zero characters. So, change to VARCHAR, put a few spaces in the Default and increase the length to 21,000. You may like to use HeidiSQL ;) )

Im going home now!

cheers