[SOLVED] Show all Followups-Description

livelinux · 2023-08-22 10:16:24

Good day, fellow GLPI Users,
we use GLPI 10.0.9 and a colleague has "Followups-Description" field in his saved search he uses.
The problem is that only some followups are being shown.

I presume that followups too long to be shown in the table field are hidden.
Where should I configure GLPI to see all followups or even their beginnings?

No worries,
Pawel

Last edited by livelinux (2023-08-22 14:20:26)

livelinux · 2023-08-22 10:42:32

It seems that when a followup contains lowercase polish letter "ą", the whole followup is not visible.
Thus solution may be easy: replace all occurences of "ą" in 'glpi_itilfollowups.content' column with "a".
Could there be an other solution, maybe?

Last edited by livelinux (2023-08-22 12:46:00)

cconard96 · 2023-08-22 12:58:51

I cannot recreate the issue. The search uses a LIKE operator to search the fields for the value and it is accent-insensitive by default so ą and a are seen the same way. The only way this would be different for you is if the table was somehow using the wrong collation.
Tables in GLPI 10 should be using utf8mb4_unicode_ci as the collation and utf8mb4 as the charset. The previous version used utf8_unicode_ci as the collation and utf8 as the charset, but while this will still work in GLPI 10, is not recommended and super-admin users are given a warning on their home screen to perform the migration. If your table(s) have a collation containing "_bin", then accents would be treated differently than the base character.

By default, there is a 250 character limit for text results in the search result display. When it is over that limit, there should be an icon in the field that lets you see the full content.
This limit can be changed in Setup > General > General setup tab with the option "Default characters limit".

livelinux · 2023-08-22 14:19:30

cconard96 wrote:

I cannot recreate the issue. The search uses a LIKE operator to search the fields for the value and it is accent-insensitive by default so ą and a are seen the same way. The only way this would be different for you is if the table was somehow using the wrong collation.
Tables in GLPI 10 should be using utf8mb4_unicode_ci as the collation and utf8mb4 as the charset. The previous version used utf8_unicode_ci as the collation and utf8 as the charset, but while this will still work in GLPI 10, is not recommended and super-admin users are given a warning on their home screen to perform the migration. If your table(s) have a collation containing "_bin", then accents would be treated differently than the base character.
By default, there is a 250 character limit for text results in the search result display. When it is over that limit, there should be an icon in the field that lets you see the full content.
This limit can be changed in Setup > General > General setup tab with the option "Default characters limit".

Thank you for your reply.
I checked the glpi database: tables and columns have the right collation and charset. They were migrated during upgrade. And I can see that icon when followups-description is too long.
I marked this topic as solved, because I think we can live without that "ą". I put:

UPDATE glpi_itilfollowups SET content = REPLACE(content, 'ą', 'a')

into cron and every occurences of "ą" are replaced.

Last edited by livelinux (2023-08-22 14:19:55)

Forum GLPI-Project

Announcement

#1 2023-08-22 10:16:24

[SOLVED] Show all Followups-Description

#2 2023-08-22 10:42:32

Re: [SOLVED] Show all Followups-Description

#3 2023-08-22 12:58:51

Re: [SOLVED] Show all Followups-Description

#4 2023-08-22 14:19:30

Re: [SOLVED] Show all Followups-Description

Board footer