Ticket UI dosn't work after a custom field is aded to columns for displaying

andrea_86

I created a custom List and then added it to the ticket form. After that I modified the tickets view under Setings->Tickets->Queues adding the new field to the "Open" Ticket Queues. From this moment i can't see anything on the list.

The field is correctly viewed in the ticket details as show

On the ticket list, if I use the "Open/open" view (without the new field) the ticket appear correctly

But if i go to the "Open" view no ticket are displayed

Checking the error log I found this:

PHP Fatal error: Uncaught InconsistentModelException: Unable to prepare query: Unknown column 'B2.module' in 'field list'

Table alias B2 referrer to

LEFT JOINost_ticket__cdataB2

that dosn't have any column 'module'. (it has ticket_id,subject,priority)
Is something gone wrong in the custom field creation?

KevinTheJedi

andrea_86

You will need to drop the _ticket__cdata table, run cron manually a bunch of times until the table is few crested and fully repopulated with data, and retest. You have to run cron multiple times as the data is repopulated in batches.

Cheers.

andrea_86

Thanks for your answer.
I've launched the cron several times (over than 20 times)

php -f cron.php (also tried with sudo)

but table isn't created.

Any other suggestion?

KevinTheJedi

andrea_86

Did you drop the _ticket__cdata table or a different table? Are you using a tool like HeidiSQL or SequelAce to view the database? If so, you may need to reload the tool to see the latest changes.

The full command is:

php-command /path/to/osTicket/api/cron.php

Where php-command is the php command that points to the version of PHP your osTicket is running. When in doubt use the full path to your PHP.

Cheers.

andrea_86

Update from previous.

The cron wasn't working because the database user didn't have enough privileges for create table and alter structure.
Probably this was the cause of the previous writing failure(when i created the field)

I removed high privileges from that user for security reason but evidently this is an error with osTicket webapp.

Tank you very much for helping me

KevinTheJedi

andrea_86

So issue resolved? The table was finally recreated and fully repopulated?

Cheers.