PHPJunkyard support forum

Hesk : 2.7.5
Mod : 3.2.4

Error when updating

"An error occurred! (Error Code: 31)
Could not execute query: ALTER TABLE `tickets` ADD KEY `statuses` (`status`). MySQL said: Key column 'status' doesn't exist in table"

Got this error when run database validation

"One or more columns / tables are not properly configured in your database. Please open a topic at the PHP Junkyard Forums with this information for assistance."



1.5.0
Column Exists: users.active Failure
1.6.0
Column Exists: users.notify_note_unassigned Failure
Table Exists: settings Failure
1.7.0
Table Exists: verified_emails Failure
Table Exists: pending_verification_emails Failure
Table Exists: stage_tickets Failure
2.2.0
Column Exists: statuses.IsAutocloseOption Failure
Column Exists: statuses.Closable Failure
2.3.0
Column Exists: service_messages.icon Failure
Column Exists: statuses.Key Failure
Column Exists: tickets.latitude Failure
Column Exists: tickets.longitude Failure
Column Exists: stage_tickets.latitude Failure
Column Exists: stage_tickets.longitude Failure
Column Exists: categories.manager Failure
Column Exists: users.permission_template Failure
Table Exists: permission_templates Failure
Column Exists: permission_templates.id Failure
Column Exists: permission_templates.name Failure
Column Exists: permission_templates.heskprivileges Failure
Column Exists: permission_templates.categories Failure

Are you updating from a previous version of Mods for HESK, or is this a clean installation?

Yes sir, updating from previous, now using ver 2.3.5 still problem exist

Are those the only lines that fail in the database validation, or does everything after 2.3.0 pass?

from database validation, get this error when install

An error occurred! (Error Code: 31)
Could not execute query: ALTER TABLE `e_tickets` ADD KEY `statuses` (`status`). MySQL said: Key column 'status' doesn't exist in table

Successfully reverted database to before the installation/update.

problem solved by renaming column

ALTER TABLE `tickets` CHANGE `status_int` `status` INT(11) NOT NULL;

You must have somehow been in a bad state if you still had the status_int column as that was used a long time ago haha. Glad to hear you found the issue.

new problem
cannot find or create new ticket.. admin panel can login..

View existing ticket

Error: Ticket not found! Please make sure you have entered the correct tracking ID!

Submit a ticket

Error:

Can't execute SQL
Please notify webmaster at

Turn on debug mode in settings and then try to submit a ticket again. The failing query will be shown.

Get this error when submit new ticket

Error:

Can't execute SQL: SELECT `text` FROM `text_to_status_xref` WHERE `status_id` = AND `language` = 'English'
MySQL said:
You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'AND `language` = 'English'' at line 2

Sorry for so many question

It looks like the ticket status isn't being properly set, which causes the invalid SQL. Is your helpdesk available publicly? If so, could you please send me the following via private message?

• Helpdesk URL
• Helpdesk Admin User/Pass
• FTP User/Pass (to make changes to test)