[Phpgroupware-tracker] [bugs #3643] select box filters not stored in nextmatch namespace cause problems when multiple nextmatches on one page

[Dave Hall]

This mail is an automated notification from the bugs tracker
 of the project: phpGroupWare.

/**************************************************************************/
[bugs #3643] Latest Modifications:

Changes by: 
                Dave Hall <address@hidden>
'Date: 
                Sun 06/06/2004 at 23:40 (Australia/Melbourne)

            What     | Removed                   | Added
---------------------------------------------------------------------------
         Assigned to | None                      | Caeies







/**************************************************************************/
[bugs #3643] Full Item Snapshot:

URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=3643>
Project: phpGroupWare
Submitted by: Johnson
On: Fri 05/16/2003 at 13:07

Category:  eTemplates
Item Group:  None
Severity:  5 - Average
Priority:  5 - Normal
Resolution:  None
Assigned to:  Caeies
Status:  Open
Component Version:  None
Platform Version:  None
Reproducibility:  None


Summary:  select box filters not stored in nextmatch namespace cause problems 
when multiple nextmatches on one page 

Original Submission:  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













For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=3643>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/