I found following errors in my recent log entries:

Unknown column 'autoassign' in 'field list' query: SELECT clid, name, path, status, integrate_email, server_name, server_username, server_password, mailfrom, mailbox, protocol, extra, port, notes, autoassign, autosubscribe, domains FROM support_client WHERE clid = 7 in /home/XXX/XXX/modules/support/support.module on line 379.

What's that about?

Comments

jeremy’s picture

jeremy commented

You are filing this issue against the 1.1 version of the module, but this field was added in 1.2. If you've recently upgraded, don't forget to run update.php.

filpet’s picture

filpet commented
Status: Active » Fixed

It seems that the update removed the error!
Thx!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

jwilson3’s picture

jwilson3
Primary language English
Location Ecuador
commented
Status: Closed (fixed) » Active

I followed the upgrade from jobtrack instruction to the T, and have run into this error.

I was sure to update to jobtrack 1.6-rc1, run update.php. then disable jobtrack, and enable support.

what can i do to get this extra field added (by hand).

jwilson3’s picture

jwilson3
Primary language English
Location Ecuador
commented
Title: Error » inconsitent upgrade from jobtrack

I further investigated the issue, and sure enough, the jobtrack.install file included in 1.6-rc1 file has no mention of the additional column 'autoassign'.

Looking at the schema as well as the support_install() function in the current support.install file, it looks like if you upgrade from Jobtrack, it has the following inconsistencies with users installing a vanilla version of support.

  • missing autoassign column in the support_client table,
  • autoassign index on the support_client table,
  • weight of the support module doesn't get set to 10 the system table.

Sorry, that I cant really supply a "clean" patch for this, but in liu of that, here's some SQL for mysql you can run by hand to fix the issues

ALTER TABLE {support_client} ADD autoassign VARCHAR(255) NOT NULL COMMENT 'Optionally assign new tickets to this user.' AFTER port;

ALTER TABLE {support_client} ADD INDEX (autoassign);

UPDATE {system} SET weight = 10 WHERE name = 'support'

I also changed the title of this issue here to something more descriptive.

BTW: Thanks for a WONDERFUL set of modules (views integration, nag, sms, etc). We're using them and like them a lot!

jeremy’s picture

jeremy commented
Status: Active » Fixed

The upgrade instructions were correct for the 1.0 release of the support module, but no longer correct now that there have been updates that further changed the schema. I updated the documentation to reflect this: when upgrading from jobtrack you have to first install the 1.0 release of the support module, and then upgrade it to the latest release of the support module. (Directly running the above queries will work for now, but as future development happens the schema will continue to change.)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.