View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0022195 | mantisbt | html | public | 2017-01-13 17:29 | 2017-01-31 04:05 |
Reporter | AeXiPHiXiON | Assigned To | atrol | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Product Version | 1.3.4 | ||||
Summary | 0022195: adding url to description and notes in report issue breaks issue view | ||||
Description | With "make_links" set to ON, the url below breaks the issue when added to description, the issue can no longer be viewed. the issue can be edited. When it is added to notes it can no longer be edited and can only be deleted. If make_links is OFF no issue, just displays as text. Issue occurs with or without a tag, trunking the second half of the url does not have an issue. $g_html_make_links = ON; | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
AeXiPHiXiON, I was not able to reproduce your problem with a fresh install of the latest stable MantisBT release (1.3.5 and 2.0.0 at the moment). BTW,
Instead of setting to ON, set it to the equivalent LINKS_SAME_WINDOW or remove the setting from config_inc.php as this is the default setting. I recommend that you upgrade to the latest (download from [1]). If after doing so the problem persists, do not hesitate to reopen the issue and provide detailed step-by-step instructions to reproduce the issue; the following additional information may also be useful:
|
|
yes, adding that URL breaks both 1.3.5 and 2.0.0. this URL does not break, adding the "=" after query causes the fail Using all default settings from unmodified clean install. Installed on AIX 7100-04-03-1642. Using chrome from Windows 7. rpm's compiled by perzl.org httpd-2.4.4-2 |
|
i tested against a newer MySQL DB and still fails but a little different. The DB is on a remote host. Seems like an issue with MySQL. clean install from unmodified MantisBT 1.3.5 rpm's compiled from www-frec.bull.com mysql privileges |
|
Are there any errors or warnings in logs of web server or database? |
|
added these entries one at a time until I got the httpd error below. attached the sql log and mysql vars. did not see any errors in the sql error log ok ok ok this URL gives me an httpd error add again, and another seg fault The seg fault appears to occur after the update when mantis is doing a select and trying to display the data, sql log during this time frame is attached [Mon Jan 16 13:37:21.915537 2017] [core:notice] [pid 21627000:tid 1] AH00052: child pid 31260826 exit signal Segmentation fault (11) The browswer url is, http://ganglia/mantisbt135/view.php?id=1 The browser error is The ganglia page isn’t working ganglia didn’t send any data. The UPDATE appears to be successful as the URL actually makes it into the database. mysql> SELECT * FROM mantis_bug_revision_table WHERE bug_id=1 AND type=1 AND bugnote_id=0 ORDER BY timestamp DESC LIMIT 1; https://gpc.service-now.com/nav_to.do?uri https://gpc.service-now.com/nav_to.do?uri=change_request.do%3Fsys_id DAL850A duuapdrkroora01 16,384 1.00 1 OraProc |
|
Where did you see this? There a some known issues in PHP 5.5.17 on some platforms in some of the functions (dealing with regular expressions) where I think they might cause the issue. I recommend to try a newer PHP version. It seems at the moment that there is hardly any thing we can do for you in MantisBT. |
|
it was a php issue. updated php to 7.0.13 and it is resolved. |
|
i did try php 7.1 but that broke mantisbt completely. |
|
Thanks for the feedback
PHP 7.1.0 is quite new and it will certainly take some time until it can be used in production environment. There are also some incompatible changes in PHP 7.1 that will be fixed in future Mantis version, e.g. |
|
Upgrading to 7.0.14-2 also breaks it with this error. no other rpms were changed. rolling back to 7.0.13 fixes it and continues to work with no issues. php binary rpms for AIX downloaded from bull.com Invalid form security token. This could be caused by a session timeout, or accidentally submitting the form twice |
|