phpGroupWare - Bugs: bug #3643, select box filters not stored in...
You are not allowed to post comments on this tracker with your current authentication level.
bug #3643: select box filters not stored in nextmatch namespace cause problems when multiple nextmatches on one page
Submitter: | Johnson <jecinc> | ||
Submitted: | Fri 16 May 2003 01:07:00 PM UTC | ||
Category: | eTemplates | Item Group: | None |
Severity: | 3 - Normal | Priority: | 5 - Normal |
Status: | None | Privacy: | Public |
Assigned to: | Caeies | Open/Closed: | Open |
Component Version: | None | Operating System: | None |
Reproducibility: | None | Planned Release: | None |
Fixed Release: |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
CC list is empty
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2004-06-06 | skwashd | Assigned to | None | Caeies | |
2004-01-20 | powerstat | Assigned to | #2883 | None | |
2003-05-16 | #2883 | Assigned to | None | None |
Powered by Savane 3.13-d3ae.
Corresponding source code
nextmatch select box filters value array isn't stored in namespace, they are just stored in $sel_options
This creates problem when multiple nextmatchs are used one one page (or in tabs) and you want the same filter (ie accounts) but with a different null display (ie you want one filter to include 'Show all..' and another filter does not)
I discovered this problem with a custom nextmatch template based on the template for the default nextmatch widget but it seems to apply to the default nextmatches too