Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.When I first installed JobTrack, the admin menus showed options for Permissions and Settings/Config. I created a client through the client form, and created a new job issue via the node/add. When attempting to view jobs, an error was displayed saying re: the select statement -- could not find column "myclient". I used the same name for path as I had for the client name, so do not know which part of that process failed. (Couldn't access MySQL at that point to check.)
I disabled the module. Uninstalled the module, hoping to try with clean module install. Even after unistalling the module, it still showed in admin, and files remained on server. I logged out of the site, and back in. I re-enabled module (and saved).
At this point, the only option through admin is for permissions. The settings/config option is now missing, so I cannot again set up a client. (The content type also does not appear on the node/add page.)
I again disabled the module, unistalled the module (through admin UI), and this manually deleted the files on server. Then, uploaded the module, unpacked the files, enabled the module. Assumed I had a clean install.
Again, the Settings/Config option missing. Only permissions is there, and as before, the permissions are set as desired.
[I have always been logged in as super admin.]
Drupal 6.9; LAMP
Thank you for the assistance (and for this great module!).
Comments
Comment #1
greta_drupal commentedComment #2
greta_drupal commentedFurther clarification:
The error is occurring when clicking the "Job ticket" menu link, which should be bringing up the summary of cases (view of query results). "dcpca" is the 'client name' and the 'path'. (NOTE: When completing the form, I used all uppercase "DCPCA" for the name, and lowercase "dcpca" for the path.)
Full error message:
* user warning: Unknown column 'dcpca' in 'where clause' query: SELECT COUNT(*) FROM node n LEFT JOIN jobtrack_ticket t ON n.nid = t.nid INNER JOIN node_comment_statistics l ON n.nid = l.nid INNER JOIN users u ON n.uid = u.uid LEFT JOIN comments c ON n.nid = c.nid WHERE (c.status = 0 OR c.status IS NULL) AND n.status = 1 AND n.type = 'jobtrack_ticket' AND client = dcpca AND t.state != 4 in /home/myaccount/public_html/DCPCA/sites/all/modules/jobtrack/jobtrack.module on line 1215.
* user warning: Unknown column 'dcpca' in 'where clause' query: SELECT DISTINCT(n.nid), n.title, n.type, n.changed, n.uid, u.name, GREATEST(n.changed, l.last_comment_timestamp) AS last_updated, l.comment_count, t.state, t.priority, t.assigned FROM node n LEFT JOIN jobtrack_ticket t ON n.nid = t.nid INNER JOIN node_comment_statistics l ON n.nid = l.nid INNER JOIN users u ON n.uid = u.uid LEFT JOIN comments c ON n.nid = c.nid WHERE (c.status = 0 OR c.status IS NULL) AND n.status = 1 AND n.type = 'jobtrack_ticket' AND client = dcpca AND t.state != 4 ORDER BY last_updated DESC LIMIT 0, 50 in /home/myaccount/public_html/DCPCA/sites/all/modules/jobtrack/jobtrack.module on line 1215.
Comment #3
greta_drupal commentedP.S. -- I have "Recent Comments" block enabled, and the job ticket teases are showing there. And, when clicked, it does successfully display that node.
Comment #4
jeremy commentedPlease try the -dev tarball, I am unable to duplicate your bug with the latest release. I installed the module, enabled it, created a single client, created a single issue, then clicked 'Job tickets' and was taking to a view of the ticket listing with that ticket visible.
I do not see any way that the jobtrack module will build the query that you are reporting in your error. This portion of your query: "AND client = dcpca", is what should not be possible -- "client" should always be a number, never a name. I do not see anywhere that this could get set to the path which is what appears to be happening for you. There was an error in the 1.0 release in which the menu cache wasn't being flushed, and I assume somehow this is causing your error -- this is fixed in the dev tarball (and I will roll a new release).
I have added additional error checking to try and catch should things get into this state.
Comment #5
jeremy commentedPlease try again with the 6.x-1.1 release. Be sure to run update.php, and see if this resolves your problems.
Comment #6
greta_drupal commentedI had run update.php before; but, I also had uninstalled and reinstalled a couple times and might not have run it the last reinstall. I just did so and the error has cleared.
Thank you for replying (and so quickly!), Jeremy. This is a great module, and I appreciate all involved for offering it. Keep up the good work!
Comment #7
jeremy commentedBe sure you're running the 1.1 release, as it fixes one important bug. Anyway, glad it's working for you.
Comment #8
greta_drupal commentedYep. I upgraded. Very nice module; just what I needed.