aMule Bug Tracker - aMule
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000686aMuleSearchpublic2005-12-05 00:002005-12-09 23:46
ReporterJacobo221 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionopen 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Fixed in Revision
Operating System
Summary0000686: extension parameter is working wrong
DescriptionIT should filter all files who's text AFTER THE LAST DOT is the text in the input box. but instead, it is just acting the same way he filter does. it will filter all files containing the text anywher in the filename.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2005-12-05 00:00Jacobo221New Issue
2005-12-05 01:24XaignarNote Added: 0001547
2005-12-05 02:31Jacobo221Note Added: 0001555
2005-12-09 23:46KryNote Added: 0001615
2005-12-09 23:46KryStatusnew => closed

Notes
(0001547)
Xaignar   
2005-12-05 01:24   
That would be a server-side bug.
(0001555)
Jacobo221   
2005-12-05 02:31   
how about filtering this locally?

yet there is another problem:
if someone is stupid enough to select for example "Type: Audio" and "Extension: txt", obviously, no results will (uhm, SHOULD. if lug did its job) be shown. Therefore, Extension should only be enabled when "Type: Any".
(0001615)
Kry   
2005-12-09 23:46   
Extensions and type are local-side and sevrer side, and thus kept independant.

As for filtering it locally, no, I don't think so. Server-side responses should always be delivered.