Home > Mantis Application > Mantis Application Error 11

Mantis Application Error 11

This could be caused by a session timeout, or accidentally submitting the form twice. You can also click an option from the menu bar to go directly to a new section." i cannot visit "view_all_bug_page.php and my_view_page.php" but other pages it works. We already have a Jenkins build server running on it and Jenkins has a Mantis plugin which is functional.http://jenkins-ci.org/Thanks again,-Ed MantisBT Version: 1.2.10Schema Version.: 183Host..................: Red Hat Enterprise Linux 5.2PhP...................: 5.2.15 Two projects have diffent category. http://edvinfo.com/mantis-application/mantis-application-error-503.html

We apologize for the inconvenience. I was playing with categories and projects as I try and understand the best architecture. Everythig was good, but suddenly I can't report an issue anymore. Commit has been tested on: FF 2.0.14 FF 3.0.4 IE 8.0.6001.18241 IE 6.0.2900.5122 GC 0.4.154.23 Opera 9.51.10081 mod - core.php [Diff] [File] MantisBT: master-1.1.x 161a677e Timestamp: 2008-11-24 14:11:42 Author: jreese [Details] https://www.mantisbt.org/bugs/view.php?id=6736

Apache server and Mantis 1.1.2. ~0018291 mkornatzki (reporter) 2008-07-03 11:35 i can reproduce the error with version 1.2.0a1. Please recheck your inputs. I hit Back (got back the form with all the fields filled in), tried to submit again, and got the error again.

mt_rand() ); switch ( $g_show_action ) { case BOTH: if ( ( null !== $p_user_id ) && ( ON == user_pref_get_pref( $p_user_id, 'advanced_' . $p_action ) ) ) { return 'bug_' If you do not have a proxy server in your set up, feel free to reopen this issue and attach more information about your network setup, your server application/versions, the browser/browsers When requesting the bug submit page, a 302 not modified header is being sent back to the client which is why the same id is be passed back. ~0019765 secteur13 (reporter) any idea?

Is there a resolution? i made the tests with ie7 ~0018563 grangeway (reporter) 2008-07-15 15:41 mkornatzki , Can you email me [email protected] a copy of the text that is failing? (if it's not company confidential Anonymous Login ProjectAll Projects mantisbt MantisTouch Mylyn Connector Plugin - agileMantis Plugin - CsvImport Plugin - CustomerManagement Plugin - EmailReporting Plugin - FilterPageEdit Plugin - InlineColumnConfiguration Plugin - LinkedCustomFields Plugin - check over here Bug does not exist on Firefox 2,3 for windows, or IE 7 ~0018184 grangeway (reporter) 2008-06-25 18:57 Does this still occur in later builds e.g. 1.2.0 alpha? ~0018288 mah (reporter) 2008-07-03

What do you think? (0026904) ibs (developer) 2013-11-26 10:35 aiv, and thank for 'Lazarus Form Recovery add-on for Firefox' (0027461) ibs (developer) 2014-01-14 11:05 edited on: 2014-01-14 11:06 dear aiv, 12381, 12492 As the common reason of 2800 error is session timeout (session files are cleaned on the server by garbage collector or session variables are passed away by any reason) the mechanism Notes Issue History Date Modified Username Field Change 2006-02-21 11:26 edroi New Issue 2008-06-25 17:20 mettaben Note Added: 0018182 2008-06-25 17:35 mettaben Note Added: 0018183 2008-06-25 18:57 grangeway Note Added: 0018184 Thanks. ~0019968 pangea (reporter) 2008-11-21 05:03 I get the same situation as dplinnane.

There you can correct whatever problems were identified in this error or select another action. https://www.mantisbt.org/bugs/view.php?id=19998 The application error dump confounds users. Reading the changes I have the impression that the correction is not appropriate: too many lines commented out, than IE case handled with "default" case, meaning caching. ~0019964 dplinnane (reporter) 2008-11-21 For all forms that are protected by "form security token" (report page, add bug note etc.) a little bit of javascript code was added to handle the following: * when submitting

I believe it asked for a category and I selected and then the Issue essentially became corrupt. check over here I could not reproduce the problematic situation, and suggest this change is introduced on the site and we see how it works. (0027616) aiv (administrator) 2014-01-22 19:55 Second part of 24039#c27579 With PHP default values, sessions created more than 1440 seconds (24 minutes) ago have a 1% chance to be invalidated each time a new session is initialized. I will keep checking email.-Ed Attachments Users do not notice it, but if you scroll the browser to the far right, displays red text "A necessary field "SVN Revision Resolved" was

We apologize for the inconvenience. I'm using 1.1.4, patch mentionned in 0009691 is present, but we randomly have the error when trying to report a bug. All reported bugs of the project have been changed to "(none category)". http://edvinfo.com/mantis-application/mantis-application-error-805.html I am unable to access it or any page that tries to display it, giving the aforementioned issue application error.

This will fix the problem with being unable to report multiple issues in a row, but will unfortunately prevent IE from saving what was typed into the form if you make As a workaround, instead of using the "Change Status To" button, please use the Edit button and pick a new Category from the list, select the New status then click the Further references and reading: MantisBT issues 12381, 12492, 13106, 13246 (0026903) ibs (developer) 2013-11-26 10:33 aiv, Thanks for the explanation :) >The way when we changing session timeout - is a

by hand-crafting the URL (CSRF attack) Expired PHP session In the first two instances, MantisBT's behavior is by design, and the response as expected.

The provided information is not sufficient to provide any help in resolving the issue. Is there any possibility to remove this timeout completely without its expanding? However is it possible to store data somewhere (a cookie for example) so it's not lost in case of an error? I much prefer Mantis to Bugzilla.Thanks again,-EdMy unmodified config_defaults_inc.php set $g_display_errors: /** * --- error display --- * what errors are displayed and how? * The options for display are: *

I put log_event calls in bug_report_page.php and in form_api.php. However, when I go to project B, everything seems ok, until I want to submit a bug for project B. But it seems to be more consistent at the moment (note that I first didn't have any problem). weblink i cannot view all project, but some project works.

It's provoked when a user of an old version (in my case 1.0.6) uses the 1.1.4 version without having clean the internet cache. i will share this for someone who has same problem with me.