I been having this for quite some time and was unable to solve it . I've been waiting for a version (my current is v1.12.5 (933bb1f) ) that solves it.
Here is the log
[SELECT A1.number AS number, A1.ticket_id AS ticket_id, A1.source AS source, A1.created AS created, A3.subject AS cdata__subject, A1.isoverdue AS isoverdue, A4.name AS user__name, A3.priority AS cdata__priority, A5.firstname AS staff__firstname, A5.lastname AS staff__lastname, A6.name AS team__name, A1.team_id AS team_id, A1.isanswered = '0' AS 2GkBZxz, (SELECT COUNT(R0.id) AS count FROM ost_thread Q7 JOIN ost_ticket Q8 ON (Q7.object_type = 'T' AND Q7.object_id = Q8.ticket_id) LEFT JOIN ost_thread_entry R0 ON (Q7.id = R0.thread_id) WHERE Q8.ticket_id = A1.ticket_id AND NOT R0.flags & 4 != 0) AS _thread_count, (SELECT COUNT(R1.id) AS count FROM ost_thread Q7 JOIN ost_ticket Q8 ON (Q7.object_type = 'T' AND Q7.object_id = Q8.ticket_id) LEFT JOIN ost_thread_entry R0 ON (Q7.id = R0.thread_id) LEFT JOIN ost_attachment R1 ON (R1.type = 'H' AND R0.id = R1.object_id) WHERE Q8.ticket_id = A1.ticket_id AND R1.inline = 0) AS _att_count, COALESCE(A5.firstname, A5.lastname, A6.name, 'zzz') AS assignee FROM ost_ticket A1 JOIN (SELECT Q7.ticket_id, Z1.relevance AS relevance FROM ost_ticket Q7 JOIN ost_ticket_status Q8 ON (Q7.status_id = Q8.id) LEFT JOIN ost_thread R0 ON (R0.object_type = 'T' AND Q7.ticket_id = R0.object_id) LEFT JOIN ost_thread_referral R1 ON (R0.id = R1.thread_id) LEFT JOIN ost_staff R2 ON (R1.object_type = 'S' AND R1.object_id = R2.staff_id) LEFT JOIN ost_team R3 ON (R1.object_type = 'E' AND R1.object_id = R3.team_id) LEFT JOIN ost_department R4 ON (R1.object_type = 'D' AND R1.object_id = R4.id) JOIN (SELECT COALESCE(Z3.object_id, Z5.ticket_id, Z8.ticket_id) as ticket_id, Z1.relevance FROM (SELECT Z1.object_id, Z1.object_type, MATCH (Z1.title, Z1.content) AGAINST (930130 IN NATURAL LANGUAGE MODE) AS relevance FROM ost__search Z1 WHERE MATCH (Z1.title, Z1.content) AGAINST (930130 IN NATURAL LANGUAGE MODE) ORDER BY relevance DESC) Z1 LEFT JOIN ost_thread_entry Z2 ON (Z1.object_type = 'H' AND Z1.object_id = Z2.id) LEFT JOIN ost_thread Z3 ON (Z2.thread_id = Z3.id AND Z3.object_type = 'T') LEFT JOIN ost_ticket Z5 ON (Z1.object_type = 'T' AND Z1.object_id = Z5.ticket_id) LEFT JOIN ost_user Z6 ON (Z6.id = Z1.object_id and Z1.object_type = 'U') LEFT JOIN ost_organization Z7 ON (Z7.id = Z1.object_id AND Z7.id = Z6.org_id AND Z1.object_type = 'O') LEFT JOIN ost_ticket Z8 ON (Z8.user_id = Z6.id)) Z1 WHERE Q7.ticket_id = Z1.ticket_id AND ((Q8.state = 'open' AND (Q7.staff_id = 20 OR R2.staff_id = 20 OR Q7.team_id IN (1) OR R3.team_id IN (1))) OR Q7.dept_id IN (14, 8, 6, 5, 9) OR R4.id IN (14, 8, 6, 5, 9)) ORDER BY Z1.relevance LIMIT 500) A2 LEFT JOIN ost_ticket__cdata A3 ON (A1.ticket_id = A3.ticket_id) JOIN ost_user A4 ON (A1.user_id = A4.id) LEFT JOIN ost_staff A5 ON (A1.staff_id = A5.staff_id) LEFT JOIN ost_team A6 ON (A1.team_id = A6.team_id) WHERE A1.ticket_id = A2.ticket_id GROUP BY A1.ticket_id ORDER BY relevance DESC LIMIT 30] Table 'osticket.ost__search' doesn't exist

1.12.5 is old. Please upgrade to latest stable (1.14.2) and re-test.

@vasco.leiria

The ost__search table should always exist. I'm not sure how this table was deleted for you however, it is very simple to fix. Login to your database, go to the ost_config table, search for key = 'reindex' AND namespace = 'mysqlsearch', and change the value from 0 to 1. After you make the change simply login to osTicket and click around a bit. You should see the table recreated and populated with data automatically. It might take some time to completely fill the table with all the data so please be patient.

Cheers.

I think it worked, one quick question: in older versions I could search for anything in the search field, now I need to put parameters to search inside the tickets. Is this normal?

Write a Reply...