0005786: Strange behaviour when applying filter

ID	Project	Category	View Status	Date Submitted	Last Update
0005786	mantisbt	filters	public	2005-06-14 22:40	2005-09-11 08:12

Reporter	eurayle	Assigned To	thraxisp
Priority	normal	Severity	minor	Reproducibility	sometimes
Status	closed	Resolution	fixed
Product Version	1.0.0a3
Fixed in Version	1.0.0rc2

Summary	0005786: Strange behaviour when applying filter
Description	When I tried to apply a filter (for example the Category), it didn't take effect. I selected a Category to filter, then after that I click the Apply Filter button, but the Issues are not filtered, while the filter for Category was still showing "any" instead of the category I selected. It usually occurs when I tried to apply filter right after I logged in. But sometimes it worked fine. This behaviour is quite annoying because it misled the users to think that after applying the filter, the listed issues correspond to that filter (especially for keyword search). However, they didn't really check the filter box to notice that actually, the filter wasn't applied successfully.
Additional Information	My Mantis setting: $g_dhtml_filters = ON Occured for both IE6 and Opera 8 browsers.
Tags	No tags attached.

polzin 2005-06-15 07:04 reporter ~0010530	"me, too"

malaussena 2005-06-15 08:35 reporter ~0010535	confirmed with IE6 and Firefox 1.0.4. Confirmed too when trying to change current project from view_all_bug page. Sometimes, nothing happens, current project still displays [All project] and list is not modified... to solve, I have to close the browser and restart.

polzin 2005-08-04 08:41 reporter ~0011067	Any idea about this one? It seems to happen quite often, as said mostly directly after login. In all cases I observed this, trying a second time worked correctly.

thraxisp 2005-08-04 16:00 reporter ~0011074	It appears that older saved filters were being rejected. This would cause the logic to reset the user cookie and re-display a default filter. The patches below change the approach to upgrade filters where possible (made in 0.18.3 or later) and present an error message for older filters. view_all_set.php -> 1.56 lang/strings_english.txt ->1.266 (add error message) core/constant_inc.php -> 1.52 (add error message)