[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Phpgroupware-tracker] [Bug #3643] select box filters not stored in nex
From: |
nobody |
Subject: |
[Phpgroupware-tracker] [Bug #3643] select box filters not stored in nextmatch namespace cause problems when multiple nextmatches on one page |
Date: |
Fri, 16 May 2003 17:04:37 -0400 |
=================== BUG #3643: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3643&group_id=509
Changes by: Ralf Becker <address@hidden>
Date: Fri 05/16/2003 at 23:04 (Europe/Berlin)
What | Removed | Added
---------------------------------------------------------------------------
Assigned to | None | ralfbecker
=================== BUG #3643: FULL BUG SNAPSHOT ===================
Submitted by: jecinc Project: phpGroupWare
Submitted on: Fri 05/16/2003 at 15:07
Category: eTemplates Bug Group: None
Severity: 5 - Major Priority: None
Resolution: None Assigned to: ralfbecker
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
No Followups Have Been Posted
CC list is empty
No files currently attached
For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3643&group_id=509