View Issue Details

IDProjectCategoryView StatusLast Update
0037374mantisbtfilterspublic2026-09-08 08:57
ReporterBGASNIER Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status confirmedResolutionopen 
Product Version2.26.0 
Summary0037374: Project selection list search does not work with special characters
Description

When trying to find a project using the search bar, nothing appears when entering certain special characters like {}()-.,\*..
Replacing each character with a space makes it work.

However, special characters like _ & work correctly.

Can you explain why only certain characters are allowed?`


Original report (in French):

Lorsque l'on souhaite se positionner sur un projet via la barre de recherche, il ne remonte rien lorsque l'on saisie certains caractères spéciaux comme {}()-.,*
Si on remplace chaque caractère par un espace cela fonctionne.
Par ailleurs, des caractères spéciaux comme _ & fonctionnent correctement.

Pouvez-vous m'expliquer la raison qui fait que seulement certains caractères sont autorisés ?
Merci,
Cordialement.

Steps To Reproduce

Have 10 projects or more, having special characters in their name.

TagsNo tags attached.
Attached Files
mantis_bug_recherche_KO.png (4,954 bytes)   
mantis_bug_recherche_KO.png (4,954 bytes)   
mantis_bug_recherche.png (16,618 bytes)   
mantis_bug_recherche.png (16,618 bytes)   

Relationships

related to 0030490 closeddregad list.js library causing CSP violation in manage_proj_edit_page.php 
related to 0030494 closeddregad list.js navigation buttons scrolling to top of page 

Activities

dregad

dregad

2026-09-08 07:06

developer   ~0071418

Last edited: 2026-09-08 07:07

Hello,

Foreign languages are not acceptable on this bug tracker.
Since I do speak French I'll translate your report this time, but please always post in English in the future. Thanks for your understanding.

The problem you described is caused by a known bug in the list.js library that we rely on to implement the search functionality in the project selector. There's even a fix available for it.

Unfortunately, we are already using the latest available release (2.3.1); the author has been inactive for years, and is not responding to messages. I am not aware of a well-maintained forks and don't have time to look for and implement an alternative library.

The only option would be to manually patch the library. We've done this in the past (see 0030494) but the problem with this approach is that the fix would not be available for instances using CDN ($g_cdn_enabled = ON).

BGASNIER

BGASNIER

2026-09-08 08:38

reporter   ~0071422

Hello,
Thanks you for your reply and explanation.
Since it's merely an irritant, we will learn to live with it.
Cdt

dregad

dregad

2026-09-08 08:54

developer   ~0071423

OK thanks for the feedback.

I'll leave this Issue open, as hopefully someday list.js will have an updated version that fixes this bug.