You are not logged in.
Glpi after updating to version 0.90 , stopped working for the Russian global search characters. Search English characters works fine.
Offline
After upgrading to GLPI 0.90.3, global search stopped working - shows no search results.
Best regards, Olo
Latest stable versions of GLPI+FI+OCS on Apache/2.2.15 (Unix) | CentOS 6.8 x64 (epel, remi, remi-php56, remi-test, home_guillomovitch) | FusionInventory Agent, FusionInventory plugin
Offline
Have you some errors in glpi's logs?
CentOS 6.5 - CentOS 7.x
PHP 5.6 - PHP 7.x - MySQL 5.6 - MariaDB 10.2 + APC + oOPcache
GLPI from 0.72 to dev version
Certifiée ITIL (ITV2F, ITILF, ITILOSA)
Offline
I have same problem. The global search in GLPI v 0.90.1 doesn't work. At result page all of catogories with phrase "No item found" In logs (Administration -> logs; event.log, mail.log,php-errors.log) there is no any warrings or errors. What can i do to resolve this problem? Help, please
Offline
No problem for me in latest stable version.
Have you errors in glpi logs? in debug mode?
CentOS 6.5 - CentOS 7.x
PHP 5.6 - PHP 7.x - MySQL 5.6 - MariaDB 10.2 + APC + oOPcache
GLPI from 0.72 to dev version
Certifiée ITIL (ITV2F, ITILF, ITILOSA)
Offline
Hi yllen! This error is only when I made a search in cyrillyc.
AS `ITEM_5`,
GROUP_CONCAT(DISTINCT CONCAT(`glpi_tickets_users_a900a61824c3906cc82f90407e525192`.`users_id`, \' \',
`glpi_tickets_users_a900a61824c3906cc82f90407e525192`.`alternative_email`)
SEPARATOR \'$$##$$\') AS `ITEM_5_2`,
IFNULL(GROUP_CONCAT(DISTINCT CONCAT(IFNULL(`glpi_groups_80a94b3f6bc6957c5f1fd062f3013524`.`completename`, \'__NULL__\'),
\'$#$\',`glpi_groups_80a94b3f6bc6957c5f1fd062f3013524`.`id`) SEPARATOR \'$$##$$\'),
\'__NULL__$#$\')
AS `ITEM_6`,
GROUP_CONCAT(DISTINCT `glpi_users_c5e682856a6d6fe48b5aed8f8b238708`.`id` SEPARATOR \'$$##$$\')
AS `ITEM_7`,
GROUP_CONCAT(DISTINCT CONCAT(`glpi_tickets_users_74690f2626744a37ace4c70dd87cea83`.`users_id`, \' \',
`glpi_tickets_users_74690f2626744a37ace4c70dd87cea83`.`alternative_email`)
SEPARATOR \'$$##$$\') AS `ITEM_7_2`,
`glpi_itilcategories`.`completename` AS `ITEM_8`, `glpi_tickets`.`due_date` AS `ITEM_9`, `glpi_tickets`.`status` AS `ITEM_9_stat
us`, `glpi_tickets`.`solvedate` AS `ITEM_10`, `glpi_tickets`.`date_mod` AS `ITEM_11`, `glpi_tickets`.`id` AS id FROM `glpi_tickets` LEFT JOIN `glpi_ticket
s_users` AS `glpi_tickets_users_a900a61824c3906cc82f90407e525192`
ON (`glpi_tickets`.`id` = `glpi_tickets_users_a900a61824c3906cc82f90407e525192`.`tickets_id`
AND `glpi_tickets_users_a900a61824c3906cc82f90407e525192`.`type`
= 1 )LEFT JOIN `glpi_users` AS `glpi_users_647c2805c3795643b0f52f520e7cdb86`
ON (`glpi_tickets_users_a900a61824c3906cc82f90407e525192`.`users_id` = `glpi_users_647c2805c3795643b0f52f520e7cdb86
`.`id`
) LEFT JOIN `glpi_groups_tickets` AS `glpi_groups_tickets_74690f2626744a37ace4c70dd87cea83`
ON (`glpi_tickets`.`id` = `glpi_groups_tickets_74690f2626744a37ace4c70dd87cea83`.`tickets_id`
AND `glpi_groups_tickets_74690f2626744a37ace4c70dd87cea83`.`type`
= 2 )LEFT JOIN `glpi_groups` AS `glpi_groups_80a94b3f6bc6957c5f1fd062f3013524`
ON (`glpi_groups_tickets_74690f2626744a37ace4c70dd87cea83`.`groups_id` = `glpi_groups_80a94b3f6bc6957c5f1fd062f3013
524`.`id`
) LEFT JOIN `glpi_tickets_users` AS `glpi_tickets_users_74690f2626744a37ace4c70dd87cea83`
ON (`glpi_tickets`.`id` = `glpi_tickets_users_74690f2626744a37ace4c70dd87cea83`.`tickets_id`
AND `glpi_tickets_users_74690f2626744a37ace4c70dd87cea83`.`type`
= 2 )LEFT JOIN `glpi_users` AS `glpi_users_c5e682856a6d6fe48b5aed8f8b238708`
ON (`glpi_tickets_users_74690f2626744a37ace4c70dd87cea83`.`users_id` = `glpi_users_c5e682856a6d6fe48b5aed8f8b238708
`.`id`
)LEFT JOIN `glpi_itilcategories`
ON (`glpi_tickets`.`itilcategories_id` = `glpi_itilcategories`.`id`
) WHERE `glpi_tickets`.`is_deleted` = \'0\' AND ( `glpi_tickets`.`entities_id` IN (\'3\') ) AND ( `glpi_
tickets`.`status` IN (\'1\',\'2\',\'3\',\'4\') AND ( `glpi_tickets`.`id` LIKE \'%ИБП%\' OR `glpi_tickets`.`name` LIKE \'%ИБП%\' OR `glpi_ticket
s`.`status` LIKE \'%ИБП%\' OR `glpi_tickets`.`date` LIKE \'%ИБП%\' OR (((`glpi_users_647c2805c3795643b0f52f520e7cdb86`.`realname` LIKE \'%ИБП%\'
OR `glpi_users_647c2805c3795643b0f52f520e7cdb86`.`firstname` LIKE \'%ИБП%\'
OR `glpi_users_647c2805c3795643b0f52f520e7cdb86`.`name` LIKE \'%ИБП%\'
OR CONCAT(`glpi_users_647c2805c3795643b0f52f520e7cdb86`.`realname`, \' \', `glpi_users_647c2805c3795643b0f52f520e7cdb86`.`firstna
me`) LIKE \'%ИБП%\' )
) OR `glpi_tickets_users_a900a61824c3906cc82f90407e525192`.`alternative_email` LIKE \'%ИБП%\' ) OR `glpi_groups_80a94b3f6bc6
957c5f1fd062f3013524`.`completename` LIKE \'%ИБП%\' OR (((`glpi_users_c5e682856a6d6fe48b5aed8f8b238708`.`realname` LIKE \'%ИБП%\'
OR `glpi_users_c5e682856a6d6fe48b5aed8f8b238708`.`firstname` LIKE \'%ИБП%\'
OR `glpi_users_c5e682856a6d6fe48b5aed8f8b238708`.`name` LIKE \'%ИБП%\'
OR CONCAT(`glpi_users_c5e682856a6d6fe48b5aed8f8b238708`.`realname`, \' \', `glpi_users_c5e682856a6d6fe48b5aed8f8b238708`.`firstna
me`) LIKE \'%ИБП%\' )
) OR `glpi_tickets_users_74690f2626744a37ace4c70dd87cea83`.`alternative_email` LIKE \'%ИБП%\' ) OR `glpi_itilcategories`.`co
mpletename` LIKE \'%ИБП%\' OR `glpi_tickets`.`due_date` LIKE \'%ИБП%\' OR `glpi_tickets`.`solvedate` LIKE \'%ИБП%\' OR `glpi_tickets`.`date_mo
d` LIKE \'%ИБП%\' ) ) GROUP BY `glpi_tickets`.`id` ORDER BY ITEM_11 DESC
Error: Illegal mix of collations for operation 'like'
Backtrace :
inc/search.class.php:903
inc/search.class.php:98 Search::constructDatas()
front/search.php:65 Search::showList()
Offline
I've opened an issue https://github.com/glpi-project/glpi/issues/719
Offline
No, friends. It is a different problems. After two days testing global search I found that it is not a Bug, maybe. Global search works only with open tickets. But it is not useful because some times I need to find tickets closed a 6 month ago.
P.S. My global search work fine with Russian words. But ticket must be open
Offline
Try to delete column with date (ticket.date, due_date, solve_date...). It's OK without these columns?
CentOS 6.5 - CentOS 7.x
PHP 5.6 - PHP 7.x - MySQL 5.6 - MariaDB 10.2 + APC + oOPcache
GLPI from 0.72 to dev version
Certifiée ITIL (ITV2F, ITILF, ITILOSA)
Offline
Try to delete column with date (ticket.date, due_date, solve_date...). It's OK without these columns?
Where?
Offline
In your personal view of ticket
CentOS 6.5 - CentOS 7.x
PHP 5.6 - PHP 7.x - MySQL 5.6 - MariaDB 10.2 + APC + oOPcache
GLPI from 0.72 to dev version
Certifiée ITIL (ITV2F, ITILF, ITILOSA)
Offline