From: Colin S. O. <co...@og...> - 2002-12-18 00:08:31
|
Hi, When installing a new version of the CVS version of mantis, I get the following error: Mantis - mantis MANTIS ERROR #200: ERROR: A required parameter to this page was not found. (gpc_api.php: line 234) Custom_config_inc.php has the following: <? $g_hostname = 'localhost'; $g_port = 3306; # 3306 is default $g_db_username = 'csogilvie'; $g_db_password = '**--**--**--**'; $g_database_name = 'csogilvie'; $g_path = 'http://www.csogilvie.uklinux.net/bugs/'; # --- email variables ------------- $g_administrator_email = 'bug...@og...'; $g_webmaster_email = 'web...@og...'; # the 'From: ' field in emails $g_from_email = 'no...@og...'; # the 'To: ' address all emails are sent. This can be a mailing list or archive address. # Actual users are emailed via the bcc: fields $g_to_email = 'no...@og...'; # the return address for bounced mail $g_return_path_email = 'ad...@og...'; $g_show_version = OFF; $g_allow_file_upload = OFF; ?> Any ideas? Colin |
From: <jea...@fr...> - 2004-07-01 15:52:34
|
unsubscribe jeff jea...@fr... |
From: Tobias P. <pol...@gm...> - 2005-06-01 07:34:48
|
Juliano Ravasi Ferraz wrote: > 1. use CSS to convert the button into something that better ressembles a > link (I prefer this, but you should be really careful because MSIE have > horrible support for CSS... a selector like input[type=submit] doesn't > work); I am interested in this, too. Do you have an example, how to do it. I know, I could figure it out usign SelfHTML, but perhaps you have already something in your mind / on your computer... Regards, Tobias -- Weitersagen: GMX DSL-Flatrates mit Tempo-Garantie! Ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl |
From: Jens H. <jen...@ya...> - 2006-04-19 20:24:01
|
Hi, I've just installed Mantis Version 1.0.2 and I've detected that it still presents all reporters in the filter list. In private project cases it may be not nice, if every user can see any other reporter, even if it is only reporter for a totally seperated project. (i.E. if you install a project for a customer, the user can see currently an other user from any other company with set up projects) I've modified project_api.php in the following way: function project_get_all_user_rows( $p_project_id = ALL_PROJECTS, $p_access_level = ANYBODY ) { .... .... $t_adm = ADMINISTRATOR; $t_users = array(); if( $c_project_id == ALL_PROJECTS ) { $t_user_id = auth_get_current_user_id(); $query = "SELECT u.id, u.username, u.realname, u.access_level FROM $t_user_table u, $t_project_user_list_table l WHERE u.enabled = $t_on AND u.access_level $t_global_access_clause AND l.user_id=u.id AND (l.project_id in (select project_id from $t_project_user_list_table where user_id = $t_user_id ))"; } else { $query = "SELECT id, username, realname, access_level FROM $t_user_table WHERE enabled = $t_on AND access_level $t_global_access_clause"; } $result = db_query( $query ); .... ..... } This works well in my configuration. I'm not sure yet, if the change interferes some other functionality. Jens |
From: Glenn H. <thr...@ma...> - 2006-04-19 21:00:45
|
Could you please file this as a bug at http://bugs.mantisbt.org/ ? ... Glenn On 19-Apr-06, at 4:23 PM, Jens Heitmann wrote: > Hi, > > I've just installed Mantis Version 1.0.2 and I've detected that it > still presents all reporters in the filter list. In private project > cases it may be not nice, if every user can see any other reporter, > even if it is only reporter for a totally seperated project. (i.E. > if you install a project for a customer, the user can see currently > an other user from any other company with set up projects) > > I've modified project_api.php in the following way: > > function project_get_all_user_rows( $p_project_id = ALL_PROJECTS, > $p_access_level = ANYBODY ) { > .... > .... > $t_adm = ADMINISTRATOR; > $t_users = array(); > > if( $c_project_id == ALL_PROJECTS ) { > $t_user_id = auth_get_current_user_id(); > > $query = "SELECT u.id, u.username, > u.realname, u.access_level > FROM $t_user_table u, > $t_project_user_list_table l > WHERE u.enabled = $t_on > AND u.access_level > $t_global_access_clause > AND l.user_id=u.id > AND (l.project_id in > (select project_id from > > $t_project_user_list_table where user_id = $t_user_id ))"; > } else { > $query = "SELECT id, username, realname, > access_level > FROM $t_user_table > WHERE enabled = $t_on > AND access_level > $t_global_access_clause"; > } > > $result = db_query( $query ); > .... > ..... > } > > > This works well in my configuration. I'm not sure yet, if the > change interferes some other functionality. > > Jens > > > > > > > > > > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, > security? > Get stuff done quickly with pre-integrated technology to make your > job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > http://sel.as-us.falkag.net/sel? > cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Mantisbt-dev mailing list > Man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev -- Glenn Henshaw Logical Outcome Ltd. e: thr...@ma... w: www.logicaloutcome.ca Mantis developer and user |
From: Jens H. <jen...@ya...> - 2006-04-19 20:37:22
|
Hi, I've just installed Mantis Version 1.0.2 and I've detected that it still presents all reporters in the filter list. In private project cases it may be not nice, if every user can see any other reporter, even if it is only reporter for a totally seperated project. (i.E. if you install a project for a customer, the user can see currently an other user from any other company with set up projects) I've modified project_api.php in the following way: function project_get_all_user_rows( $p_project_id = ALL_PROJECTS, $p_access_level = ANYBODY ) { .... .... $t_adm = ADMINISTRATOR; $t_users = array(); if( $c_project_id == ALL_PROJECTS ) { $t_user_id = auth_get_current_user_id(); $query = "SELECT u.id, u.username, u.realname, u.access_level FROM $t_user_table u, $t_project_user_list_table l WHERE u.enabled = $t_on AND u.access_level $t_global_access_clause AND l.user_id=u.id AND (l.project_id in (select project_id from $t_project_user_list_table where user_id = $t_user_id ))"; } else { $query = "SELECT id, username, realname, access_level FROM $t_user_table WHERE enabled = $t_on AND access_level $t_global_access_clause"; } $result = db_query( $query ); .... ..... } This works well in my configuration. I'm not sure yet, if the change interferes some other functionality. Jens |
From: Paul R. <pa...@ma...> - 2009-06-15 22:31:28
|
Hello, Before we release RC, I'd like to propose merging in changes in the following branch: Branch is at: http://git.mantisforge.org/w/mantisbt/paul.git?a=shortlog;h=refs/heads/15June I've been updating the name every now and again, so expect it to disappear and appear under a new name in a few days ;) Changes currently covered in this branch: * Change the way we store/handle bug objects. IIRC, the starting point for handling this was twofold: a) a large number of calls to string_attribute/string_display due to fact we can't guarantee type of field b) try to fix the due_date functionality * Better support within mantis for php 5.3 which is due out soon. For example some function (ereg, split) are deprecated in php5.3 - whilst not visible, this does mean we hook the error handler, whenever we hit a split/ereg call (and ereg *was* being used for some display functions * PHP CodeSniffer validation - I've recently over the last few months had a go at running php codesniffer ( http://pear.php.net/package/PHP_CodeSniffer/docs ) with a custom mantis ruleset, with the aim to implement some rules automatically that checks against some of our coding guidelines ( http://www.mantisbt.org/guidelines.php ) and some of the generic performance sniff's implemented by codesniffer. I've recently set up phpundercontrol (as a continuous integration platform) that can we used to run and other automated builds * PHP Doc All of the core API's now pass phpdoc validation (i.e. all functions have a phpdoc comment in a valid format) - some of the wiki classes are still throwing up errors. This is something to hopefully help plugin authors, albeit, the wording of the documentation needs to be improved in some cases. Phpdoc output for mantis can be found at http://www.mantisforge.org/dev/phpdoc/ * Library changes There's a small tidyup of what we do with stored libraries. For each library there is a readme.mantis file that indicates changes we've made to the library (if any) - this is a more detailed version of the summary file in the library/ directory. In addition, following the approach used by moodle, this readme file lists any changes to the directory structure - for example remove tests/ and other unneeded files from the libraries (in the past it's not been unknown for tests/ folders to contain code with security risks (for example mantis was affected by http://www.juniper.net/security/auto/vulnerabilities/vuln16187.html) * Graph Plugin The code used within mantis to generate graphs (using jpgraph which is not gpl), has been moved to a plugin. In addition, a compatible graph library that is compatible with gpl has been added as an additional option. This will work out the box - the formatting of some of the new graphs for labels needs some improvment, however the base functionality to match the old jpgraph code is there. It's possible within the plugin to switch to using jpgraph for those that are able to and prefer it - I believe there might currently be a slight performance gain with jpgraph. * Performance improvement attempts: Most of these are mainly with the aim of trying to improve http://www.mantisbt.org/bugs/view.php?id=8561 - currently we have one issue on our live tracker that has around 300 comments - adding a new comment currently generates a php error message as we run out of time or memory trying to generate emails for everyone monitoring the issue In additional, have added logic to support the use of compressed jscript files in production, and development versions. I'm thinking here if we add the likes of jquery, this gives us an option to easily flip between an optimised version for end users and a developers version. Paul |
From: Gianluca S. <gi...@gm...> - 2009-06-23 21:42:23
|
On Tue, Jun 16, 2009 at 12:31 AM, Paul Richards<pa...@ma...> wrote: > Hello, > > Before we release RC, I'd like to propose merging in changes in the following branch: > > Branch is at: http://git.mantisforge.org/w/mantisbt/paul.git?a=shortlog;h=refs/heads/15June > +1. My only complain is that is a bit too much stuff for a single branch, making it harder to review. We will just see how it works after the merge ;) -- Gianluca Sforna http://morefedora.blogspot.com http://www.linkedin.com/in/gianlucasforna |
From: <daw...@ta...> - 2009-12-22 06:08:16
|
need help on the clone script the category doesn't hold the same date when I say clone. |
From: Paul R. <pa...@ma...> - 2013-09-30 20:04:20
|
Any idea why commits are linking up from repo into the bug? http://www.mantisbt.org/bugs/view.php?id=16431 |
From: Damien R. <dr...@ma...> - 2013-09-30 21:00:23
|
On 30.09.2013 22:04, Paul Richards wrote: > Any idea why commits are linking up from repo into the bug? > > http://www.mantisbt.org/bugs/view.php?id=16431 Assuming you mean "commits are *not* linking up", that's because you double-quoted the word "Fix", and the source control's regex does not take that into account. Next time don't put the quotes and it will link automatically. For the record, a bug will be linked if the commit message matches the following '/(?:bugs?|issues?|reports?)+\s+(?:#(?:\d+)[,\.\s]*)+/i' In addition, the bug will also be automatically resolved if it matches '/(?:fixe?d?s?|resolved?s?)+\s+(?:#(?:\d+)[,\.\s]*)+/i' I assumed you intentionally did not port it to master ? I thought one was supposed to fix master first, *then* back-port to 1.2.x (sic) D |
From: Julian F. <ju...@be...> - 2002-12-18 05:48:22
|
Hmm... you'll need to tell us what page you were accessing when you got the error (preferably the full URL with parameters) and how you got there. Also, what access level the user you were logged in as might be useful. Also try adding: $g_show_detailed_errors = ON; to your custom_config... that should display a little more info like the name of the parameter that is missing. Julian Colin S. Ogilvie wrote: > Hi, > When installing a new version of the CVS version of mantis, I get the > following error: > > Mantis - mantis > MANTIS ERROR #200: ERROR: A required parameter to this page was not > found. > (gpc_api.php: line 234) > > Custom_config_inc.php has the following: > <? > $g_hostname = 'localhost'; > $g_port = 3306; # 3306 is default > $g_db_username = 'csogilvie'; > $g_db_password = '**--**--**--**'; > $g_database_name = 'csogilvie'; > $g_path = 'http://www.csogilvie.uklinux.net/bugs/'; > # --- email variables ------------- > $g_administrator_email = 'bug...@og...'; > $g_webmaster_email = 'web...@og...'; > # the 'From: ' field in emails > $g_from_email = 'no...@og...'; > # the 'To: ' address all emails are sent. This can be a mailing list or > archive address. > # Actual users are emailed via the bcc: fields > $g_to_email = 'no...@og...'; > # the return address for bounced mail > $g_return_path_email = 'ad...@og...'; > $g_show_version = OFF; > $g_allow_file_upload = OFF; > ?> > > Any ideas? > > Colin > > > > ------------------------------------------------------- > This sf.net email is sponsored by: > With Great Power, Comes Great Responsibility > Learn to use your power at OSDN's High Performance Computing Channel > http://hpc.devchannel.org/ > _______________________________________________ > Mantisbt-dev mailing list > Man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev -- ju...@be... Beta4 Productions (http://www.beta4.com) |
From: Colin S. O. <co...@og...> - 2002-12-21 22:30:27
|
Hi Julian, Sorry for the delay in responding - all these pre-christmas activities have left me short of time! I'm trying to access http://www.csogilvie.uklinux.net/bugs/bug_report.php from a POST from http://www.csogilvie.uklinux.net/bugs/bug_report_page.php using an administrator account (not the default) and the returned output is: Mantis - mantis MANTIS ERROR #200: ERROR: A required parameter to this page was not found. (gpc_api.php: line 234) Full path: /backup/www/csogilvie.uklinux.net/bugs/core/gpc_api.php Line: 234 Variable Value Type p_var_name f_file string p_default NULL _FILES Array array I would suggest that you create an account and try to see it formatted better if it helps (http://www.csogilvie.uklinux.net/bugs/). Colin -----Original Message----- From: man...@li... [mailto:man...@li...] On Behalf Of Julian Fitzell Sent: 18 December 2002 05:48 To: man...@li... Subject: Re: [Mantisbt-dev] (no subject) Hmm... you'll need to tell us what page you were accessing when you got the error (preferably the full URL with parameters) and how you got there. Also, what access level the user you were logged in as might be useful. Also try adding: $g_show_detailed_errors = ON; to your custom_config... that should display a little more info like the name of the parameter that is missing. Julian Colin S. Ogilvie wrote: > Hi, > When installing a new version of the CVS version of mantis, I get the > following error: > > Mantis - mantis > MANTIS ERROR #200: ERROR: A required parameter to this page was not > found. > (gpc_api.php: line 234) > > Custom_config_inc.php has the following: > <? > $g_hostname = 'localhost'; > $g_port = 3306; # 3306 is default > $g_db_username = 'csogilvie'; > $g_db_password = '**--**--**--**'; > $g_database_name = 'csogilvie'; > $g_path = 'http://www.csogilvie.uklinux.net/bugs/'; > # --- email variables ------------- > $g_administrator_email = 'bug...@og...'; > $g_webmaster_email = 'web...@og...'; # the 'From: ' > field in emails $g_from_email = 'no...@og...'; > # the 'To: ' address all emails are sent. This can be a mailing list or > archive address. > # Actual users are emailed via the bcc: fields > $g_to_email = 'no...@og...'; > # the return address for bounced mail > $g_return_path_email = 'ad...@og...'; > $g_show_version = OFF; > $g_allow_file_upload = OFF; > ?> > > Any ideas? > > Colin > > > > ------------------------------------------------------- > This sf.net email is sponsored by: > With Great Power, Comes Great Responsibility > Learn to use your power at OSDN's High Performance Computing Channel > http://hpc.devchannel.org/ > _______________________________________________ > Mantisbt-dev mailing list > Man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev -- ju...@be... Beta4 Productions (http://www.beta4.com) ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ Mantisbt-dev mailing list Man...@li... https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |
From: Julian F. <ju...@be...> - 2002-12-22 01:59:29
|
Aha... got it! I just fixed it in CVS. The problem is that you have file uploads disabled and so bug_report_page.php doesn't display the file upload field. But the bug_report.php was expecting the field to be there in all cases. Anyway, it's optional now so it should work. Thanks for the bug report. Julian Colin S. Ogilvie wrote: > Hi Julian, > > Sorry for the delay in responding - all these pre-christmas activities > have left me short of time! > > I'm trying to access > http://www.csogilvie.uklinux.net/bugs/bug_report.php from a POST from > http://www.csogilvie.uklinux.net/bugs/bug_report_page.php using an > administrator account (not the default) and the returned output is: > > Mantis - mantis > MANTIS ERROR #200: ERROR: A required parameter to this page was not > found. > (gpc_api.php: line 234) > > Full path: /backup/www/csogilvie.uklinux.net/bugs/core/gpc_api.php > Line: 234 > Variable Value Type > p_var_name f_file string > p_default NULL > _FILES Array array > > I would suggest that you create an account and try to see it formatted > better if it helps (http://www.csogilvie.uklinux.net/bugs/). > > Colin > > -----Original Message----- > From: man...@li... > [mailto:man...@li...] On Behalf Of Julian > Fitzell > Sent: 18 December 2002 05:48 > To: man...@li... > Subject: Re: [Mantisbt-dev] (no subject) > > > Hmm... you'll need to tell us what page you were accessing when you got > the error (preferably the full URL with parameters) and how you got > there. Also, what access level the user you were logged in as might be > useful. > > Also try adding: > > $g_show_detailed_errors = ON; > > to your custom_config... that should display a little more info like the > > name of the parameter that is missing. > > Julian > > Colin S. Ogilvie wrote: > >>Hi, >>When installing a new version of the CVS version of mantis, I get the >>following error: >> >>Mantis - mantis >>MANTIS ERROR #200: ERROR: A required parameter to this page was not >>found. >>(gpc_api.php: line 234) >> >>Custom_config_inc.php has the following: >><? >>$g_hostname = 'localhost'; >>$g_port = 3306; # 3306 is default >>$g_db_username = 'csogilvie'; >>$g_db_password = '**--**--**--**'; >>$g_database_name = 'csogilvie'; >>$g_path = 'http://www.csogilvie.uklinux.net/bugs/'; >># --- email variables ------------- >>$g_administrator_email = 'bug...@og...'; >>$g_webmaster_email = 'web...@og...'; # the 'From: ' >>field in emails $g_from_email = 'no...@og...'; >># the 'To: ' address all emails are sent. This can be a mailing list > > or > >>archive address. >># Actual users are emailed via the bcc: fields >>$g_to_email = 'no...@og...'; >># the return address for bounced mail >>$g_return_path_email = 'ad...@og...'; >>$g_show_version = OFF; >>$g_allow_file_upload = OFF; >>?> >> >>Any ideas? >> >>Colin >> >> >> >>------------------------------------------------------- >>This sf.net email is sponsored by: >>With Great Power, Comes Great Responsibility >>Learn to use your power at OSDN's High Performance Computing Channel >>http://hpc.devchannel.org/ >>_______________________________________________ >>Mantisbt-dev mailing list >>Man...@li... >>https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > > > -- ju...@be... Beta4 Productions (http://www.beta4.com) |
From: Colin S. O. <co...@og...> - 2002-12-22 22:41:48
|
Julian That got it. Thanks Colin -----Original Message----- From: man...@li... [mailto:man...@li...] On Behalf Of Julian Fitzell Sent: 22 December 2002 01:59 To: man...@li... Subject: Re: [Mantisbt-dev] bug in bug_report.php when file uploading is disabled Aha... got it! I just fixed it in CVS. The problem is that you have file uploads disabled and so bug_report_page.php doesn't display the file upload field. But the bug_report.php was expecting the field to be there in all cases. Anyway, it's optional now so it should work. Thanks for the bug report. Julian Colin S. Ogilvie wrote: > Hi Julian, > > Sorry for the delay in responding - all these pre-christmas activities > have left me short of time! > > I'm trying to access > http://www.csogilvie.uklinux.net/bugs/bug_report.php from a POST from > http://www.csogilvie.uklinux.net/bugs/bug_report_page.php using an > administrator account (not the default) and the returned output is: > > Mantis - mantis > MANTIS ERROR #200: ERROR: A required parameter to this page was not > found. > (gpc_api.php: line 234) > > Full path: /backup/www/csogilvie.uklinux.net/bugs/core/gpc_api.php > Line: 234 > Variable Value Type > p_var_name f_file string > p_default NULL > _FILES Array array > > I would suggest that you create an account and try to see it formatted > better if it helps (http://www.csogilvie.uklinux.net/bugs/). > > Colin > > -----Original Message----- > From: man...@li... > [mailto:man...@li...] On Behalf Of Julian > Fitzell > Sent: 18 December 2002 05:48 > To: man...@li... > Subject: Re: [Mantisbt-dev] (no subject) > > > Hmm... you'll need to tell us what page you were accessing when you > got > the error (preferably the full URL with parameters) and how you got > there. Also, what access level the user you were logged in as might be > useful. > > Also try adding: > > $g_show_detailed_errors = ON; > > to your custom_config... that should display a little more info like > the > > name of the parameter that is missing. > > Julian > > Colin S. Ogilvie wrote: > >>Hi, >>When installing a new version of the CVS version of mantis, I get the >>following error: >> >>Mantis - mantis >>MANTIS ERROR #200: ERROR: A required parameter to this page was not >>found. >>(gpc_api.php: line 234) >> >>Custom_config_inc.php has the following: >><? >>$g_hostname = 'localhost'; >>$g_port = 3306; # 3306 is default >>$g_db_username = 'csogilvie'; >>$g_db_password = '**--**--**--**'; >>$g_database_name = 'csogilvie'; >>$g_path = 'http://www.csogilvie.uklinux.net/bugs/'; >># --- email variables ------------- >>$g_administrator_email = 'bug...@og...'; >>$g_webmaster_email = 'web...@og...'; # the 'From: ' >>field in emails $g_from_email = 'no...@og...'; >># the 'To: ' address all emails are sent. This can be a mailing list > > or > >>archive address. >># Actual users are emailed via the bcc: fields >>$g_to_email = 'no...@og...'; >># the return address for bounced mail >>$g_return_path_email = 'ad...@og...'; $g_show_version = >>OFF; $g_allow_file_upload = OFF; >>?> >> >>Any ideas? >> >>Colin >> >> >> >>------------------------------------------------------- >>This sf.net email is sponsored by: >>With Great Power, Comes Great Responsibility >>Learn to use your power at OSDN's High Performance Computing Channel >>http://hpc.devchannel.org/ >>_______________________________________________ >>Mantisbt-dev mailing list >>Man...@li... >>https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > > > -- ju...@be... Beta4 Productions (http://www.beta4.com) ------------------------------------------------------- This SF.NET email is sponsored by: Order your Holiday Geek Presents Now! Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap, MP3 Players, XBox Games, Flying Saucers, WebCams, Smart Putty. T H I N K G E E K . C O M http://www.thinkgeek.com/sf/ _______________________________________________ Mantisbt-dev mailing list Man...@li... https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |