From: Victor B. <vb...@gm...> - 2007-07-31 06:50:36
|
Hi all, I've just updated the official bug tracker with the latest CVS code, as a dry run before the Mantis 1.1.0a4 release. I've found the following issues: 1. Change Log Bug: http://www.mantisbt.org/bugs/view.php?id=8214 - grangeway 2. Issue Jump button looks strange - related to the style change - zakman Lets see if we can find any issues before we release 1.1.0a4. Regards, Victor |
From: Gianluca S. <gi...@gm...> - 2007-07-31 07:46:44
|
On 7/31/07, Victor Boctor <vb...@gm...> wrote: > > 2. Issue Jump button looks strange - related to the style change - zakman I still have around the code I tested locally (including a CSS minor tweak). Expect a fix in few minutes |
From: Victor B. <vb...@gm...> - 2007-07-31 07:48:29
|
Thanks Gianluca, check-it in and I'll apply it to the bug tracker tomorrow. On 7/31/07, Gianluca Sforna <gi...@gm...> wrote: > On 7/31/07, Victor Boctor <vb...@gm...> wrote: > > > > 2. Issue Jump button looks strange - related to the style change - zakman > > I still have around the code I tested locally (including a CSS minor > tweak). Expect a fix in few minutes > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > |
From: Gianluca S. <gi...@gm...> - 2007-07-31 08:45:04
|
On 7/31/07, Victor Boctor <vb...@gm...> wrote: > Hi all, > > I've just updated the official bug tracker with the latest CVS code, > as a dry run before the Mantis 1.1.0a4 release. > > I've found the following issues: > > 1. Change Log Bug: http://www.mantisbt.org/bugs/view.php?id=8214 - grangeway > > 2. Issue Jump button looks strange - related to the style change - zakman > I am also noticing I can't access summarey_page.php anymore :( It does not show on the menu and I get an "Access denied" message when I try to directly access it |
From: Paul <pa...@qu...> - 2007-07-31 16:43:01
|
> > 1. Change Log Bug: http://www.mantisbt.org/bugs/view.php?id=8214 - > grangeway > > Lets see if we can find any issues before we release 1.1.0a4. Fixed this earlier - could you sync bugs.mantisbt.org again. There's patches/work being done on custom fields, I'd like to rework /admin directory but I think there's value to pushing a4 out now and then adding any of that work between a4<>some beta/RC release. The only thing I think we do need to address at some point is whether we need to do anything for Unicode support for storage in non-mysql db's Paul |
From: Victor B. <vb...@gm...> - 2007-08-01 03:46:50
|
Hi all, Official bug tracker updated with latest fixes and following are the results: 1. Changelog - fixed 2. Jump Button - fixed 3. Summary Page access for Developers - fixed - this was a configuration issue. Gianluca, in the summary page, I can see we are filtering out projects that are not accessible to the logged in user, but do we filter out private issues that are not visible to the user? If not, then we should really do it for all the numbers in the summary page, but it is extra important for the new most active issues box that you added. This is because it displays the bug numbers and summaries. Please confirm if we already filter out non-accessible issues or not. On 7/31/07, Paul <pa...@qu...> wrote: > > > > 1. Change Log Bug: http://www.mantisbt.org/bugs/view.php?id=8214 - > > grangeway > > > > Lets see if we can find any issues before we release 1.1.0a4. > > Fixed this earlier - could you sync bugs.mantisbt.org again. > > There's patches/work being done on custom fields, I'd like to rework /admin > directory but I think there's value to pushing a4 out now and then adding > any of that work between a4<>some beta/RC release. > > The only thing I think we do need to address at some point is whether we > need to do anything for Unicode support for storage in non-mysql db's > > Paul > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > |
From: Gianluca S. <gi...@gm...> - 2007-08-01 06:20:31
|
On 8/1/07, Victor Boctor <vb...@gm...> wrote: > Gianluca, in the summary page, I can see we are filtering out projects > that are not accessible to the logged in user, but do we filter out > private issues that are not visible to the user? If not, then we > should really do it for all the numbers in the summary page, but it is > extra important for the new most active issues box that you added. > This is because it displays the bug numbers and summaries. Ah, the joy of private issues... I am taking care of this now: any place I can quickly check how to properly do that? |
From: Victor B. <vb...@gm...> - 2007-08-01 07:02:04
|
Hi Gianluca, See L516 in filter_api.php for an example of handling private/public issues. The following issue also seems to be a showstopper: 8215: APPLICATION ERROR 401 on MySQL with file_upload_method = DISK (1.1.0a4-CVS) http://www.mantisbt.org/bugs/view.php?id=8215 On 7/31/07, Gianluca Sforna <gi...@gm...> wrote: > On 8/1/07, Victor Boctor <vb...@gm...> wrote: > > Gianluca, in the summary page, I can see we are filtering out projects > > that are not accessible to the logged in user, but do we filter out > > private issues that are not visible to the user? If not, then we > > should really do it for all the numbers in the summary page, but it is > > extra important for the new most active issues box that you added. > > This is because it displays the bug numbers and summaries. > > Ah, the joy of private issues... I am taking care of this now: any > place I can quickly check how to properly do that? > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > |
From: Gianluca S. <gi...@gm...> - 2007-08-01 08:13:21
|
On 8/1/07, Victor Boctor <vb...@gm...> wrote: > Hi Gianluca, > > See L516 in filter_api.php for an example of handling private/public issues. > > The following issue also seems to be a showstopper: > > 8215: APPLICATION ERROR 401 on MySQL with file_upload_method = DISK > (1.1.0a4-CVS) > http://www.mantisbt.org/bugs/view.php?id=8215 Both should be fixed now |