View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0014097 | mantisbt | other | public | 2012-03-26 08:51 | 2014-09-23 18:05 |
Reporter | schoppi71 | Assigned To | dregad | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Platform | Linux SuSE Linux Enterprise Serv | OS | SuSe Linux Enterprise Server | OS Version | 10 SP2 64-Bit |
Product Version | 1.2.9 | ||||
Target Version | 1.2.10 | Fixed in Version | 1.2.10 | ||
Summary | 0014097: German 'Umlaute' with closing question mark failed | ||||
Description | If I insert in the description field two german Umlaute like üäöß? with a closing question mark mantis will fail without error message. Only a white page is shown. e.g. üä? | ||||
Tags | No tags attached. | ||||
I'm using Mantis 1.2.9 with PostgreSQL-DB 8.3.7 on Linux SuSE Linux Enterprise Server 10 SP2 64-Bit. |
|
This won't fail: there must be at least 2 german Umlaute plus a closing ? |
|
Can you please confirm the value of $g_show_queries_list in your config ? |
|
$g_show_queries_list = ON; |
|
In that case, I think the behavior you're seeing is due to the same root cause as 0013280, i.e. preg_match using a byte-based offset while the parsed string is UTF-8 (potentially multi-byte). I'll fix that later. In the meanwhile, if you set $g_show_queries_list = OFF (which by the way is in any case the recommended value), you should not experience this problem anymore. |
|
You are right! After switching $g_show_queries_list to OFF the problem is vanished. |
|
Could you test this code ? (remember to put $g_show_queries_list back to ON) |
|
Hey dregard, |
|
Only core/database_api.php |
|
I tested the new version of database_api.php and it works now. |
|
Thanks for testing ! I'll commit the changes later. |
|
Marking as 'acknowledged' not resolved/closed to track that change gets ported to master-2.0.x branch |
|
MantisBT: master 50f45ad5 2012-03-27 01:16 Details Diff |
Fix utf8 offset when logging SQL in db_query_bound The fix for 0013280 (5835572fde9df4d0837f0105c6c44c75fe64c07c) only fixed one part of the problem, i.e. when the UTF8 characters were in the SQL query itself. This commit fixes the remaining case when the string parameters contain multibyte chars. Fixes 0014097 |
Affected Issues 0014097 |
|
mod - core/database_api.php | Diff File | ||
MantisBT: master-1.2.x 094d4b27 2012-03-27 01:16 Details Diff |
Fix utf8 offset when logging SQL in db_query_bound The fix for 0013280 (5835572fde9df4d0837f0105c6c44c75fe64c07c) only fixed one part of the problem, i.e. when the UTF8 characters were in the SQL query itself. This commit fixes the remaining case when the string parameters contain multibyte chars. Fixes 0014097 |
Affected Issues 0014097 |
|
mod - core/database_api.php | Diff File |