Statuses error in 2.3.2 mods version and 2.6.4 hesk version

[manhru]

Hi,

I've tried to install the mods on hesk and every time I get this at the very beginning of installation procedure:

Could not execute query: CREATE TABLE `hesk_statuses` ( `ID` INT NOT NULL, `ShortNameContentKey` TEXT NOT NULL, `TicketViewContentKey` TEXT NOT NULL, `TextColor` TEXT NOT NULL, `IsNewTicketStatus` BIT NOT NULL DEFAULT 0, `IsClosed` BIT NOT NULL DEFAULT 0, `IsClosedByClient` BIT NOT NULL DEFAULT 0, `IsCustomerReplyStatus` BIT NOT NULL DEFAULT 0, `IsStaffClosedOption` BIT NOT NULL DEFAULT 0, `IsStaffReopenedStatus` BIT NOT NULL DEFAULT 0, `IsDefaultStaffReplyStatus` BIT NOT NULL DEFAULT 0, `LockedTicketStatus` BIT NOT NULL DEFAULT 0, PRIMARY KEY (`ID`)). MySQL said: Table 'hesk_statuses' already exists

Is obviously that the table "hesk_statuses" doesn't exists before installation. I think that the procedure at some point is looping and asking itself about a table that it created.

Hope you all can help me with it.

Thank you in advanced.

[mkoch227]

I just checked the install sql, and it looks like the table is only created once. If you try to run the installer twice, you WILL get that error (if you check your database in phpMyAdmin or another SQL database explorer, you will see hesk_statuses). You can run the uninstaller (which is available by going to the install page and clicking "Uninstall Mods for HESK"), check to make sure that the hesk_statuses table no longer exists, and try installing again.

Note: The uninstall will claim it failed when it tries to make changes to columns that don't exist in your installation; however you can safely ignore that.

[manhru]

Hi,

Sorry for my delayed response. I checked the tables before perform any installation procedure and the table isn't there. I ran the installation and the error popped up at the 2.2 version. I reload the page and the installation went all through the end. Everything seemed fine but when I tried to create a ticket an error related with keys at database level was displayed. The error said that a statuses key was missing at ticket table, I manually created the key and we could create the ticket successfully.

What I'm trying to figure out is avoid that kind of errors in the future by trying to complete correctly the installation process.

Please let me know all your thoughts!

Thanks in advanced

[mkoch227]

I'm honestly clueless why the installer would try to create the statuses table on 2.2.0, especially since the table was created way back around 1.2.0. Also, the issue with the missing key for statuses should be applied in the 2.0.0 portion of the upgrade, so long as you don't have the key already. I'm going to update the original SQL to automatically add the key when it first creates the table, though.

If you don't mind, would you be willing to create a brand new (separate) installation of HESK and try the install again? I'm curious if it happens again

[manhru]

Hi Mike!
In fact I've installed two more Hesk, one with a preexisting database (considerably smaller and simpler that this one) and everything went fine, it's working great to the date. The other one was a completely clean installation and the same result, it's working great.
It's so frustrating that your main Hesk page doesn't look awesome like the other "additional" hesk instances!
Thank you a lot Mike for all your help and follow up, I'll wait to another hesk update and try again with the mods!