Dependency Graph
View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011079 | mantisbt | bugtracker | public | 2009-10-26 06:27 | 2010-04-23 23:22 |
| Reporter | alainp | Assigned To | dhx | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | duplicate | ||
| Product Version | 1.2.0rc1 | ||||
| Summary | 0011079: Error viewing private note | ||||
| Description | User "reporter" has following error when viewing a bug with a private note : Fatal error: Maximum execution time of 40 seconds exceeded in /home/cpodm/public_html/help/core/user_pref_api.php on line 526 When the private note is deleted, the bug view page opens correctly. (User "developer" has no problem viewing the bug with the private note). | ||||
| Tags | No tags attached. | ||||
|
Can you please try upgrading to 1.2.0rc2 and if that doesn't fix your problem, could you please copy+paste approx 10 lines either side of where the error is occurring within user_pref_api.php? I can't reproduce the error you're getting and I also can't see any reason why line 526 in user_pref_api.php (of version 1.2.0rc1) would create an endless loop. Just out of interest, can you reproduce this timeout in other tickets with private bug notes? The 40 second timeout could be a simple matter of trying to view a bug with 1000 notes attached on a server that is already overloaded. |
|
|
I'll try upgrading to rc2. in the meantime, I can reproduce this on any bug, simply by making a note private and trying to access it with a "reporter" user. (Max number of notes per bug is 10). Note that my default language is not english ("french") as the lines 516 + in user_pref_api.php point to language selection./**
The problem is still happening when I switch to english, but in this case, I got a slightly different error message : This seems to me that the timeout occured elswhere in the loop : but this time is it relevant to the issue : |
|
|
Thanks for the additional detail. The bug you encountered was indeed in the second dump of code you provided. After tracing it back, it appears Victor fixed this already as part of 0010655. This patch is included in the RC2 release. I'll close this bug report as a duplicate of 0010655 (which has been completed/fixed). If you can still reproduce this problem with RC2 please reopen this bug report. Once again, thanks for reporting this problem :) |
|
|
Patched with the diff of 0010655 and it works perfectly now ! Thank you for so much efficiency ! |
|
related to
child of
duplicate of