Page 1 of 1

Unable to execute SQL INSERT INTO `hesk_stage_tickets`

Posted: Tue Dec 24, 2019 11:09 am
by caygri
Hello,

Merry Xstmas to everyone! User cant send new ticket I activate debug and I see this error. How can I fix?

Code: Select all

Errore:

Impossibile eseguire SQL: INSERT INTO `hesk_stage_tickets` ( `trackid`, `name`, `email`, `category`, `priority`, `subject`, `message`, `dt`, `lastchange`, `articles`, `ip`, `language`, `openedby`, `owner`, `attachments`, `merged`, `status`, `latitude`, `longitude`, `html`, `user_agent`, `screen_resolution_height`, `screen_resolution_width`, `due_date`, `history` , `custom1`, `custom2`, `custom3`, `custom4`, `custom5`, `custom6`, `custom7`, `custom8`, `custom9`, `custom10`, `custom11`, `custom12`, `custom13`, `custom14`, `custom15`, `custom16`, `custom17`, `custom18`, `custom19`, `custom20`, `custom21`, `custom22`, `custom23`, `custom24`, `custom25`, `custom26`, `custom27`, `custom28`, `custom29`, `custom30`, `custom31`, `custom32`, `custom33`, `custom34`, `custom35`, `custom36`, `custom37`, `custom38`, `custom39`, `custom40`, `custom41`, `custom42`, `custom43`, `custom44`, `custom45`, `custom46`, `custom47`, `custom48`, `custom49`, `custom50` , `assignedby` ) VALUES ( '2GE-NVV-8L3U', 'my name', 'my email', '1', '3', 'oiuygf', '<p>liuhg</p>', NOW(), NOW(), NULL, '213.45.174.22', 'Italiano', '0', '1', '', '', '0', 'E-0', 'E-0', '1', 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36', 1080, 1920, NULL, '' , '', '3407080395', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '' , -1 )
MySQL riporta:
Unknown column 'assignedby' in 'field list'

 

Re: Unable to execute SQL INSERT INTO `hesk_stage_tickets`

Posted: Tue Dec 24, 2019 11:22 am
by Klemen
Moving to Mods for Hesk forum.

Re: Unable to execute SQL INSERT INTO `hesk_stage_tickets`

Posted: Wed Jan 01, 2020 9:14 pm
by mkoch227
Confirmed that this is an issue. Workaround until a bugfix release is to disable the "Require customers to verify email" feature in Helpdesk settings.