View Issue Details

IDProjectCategoryView StatusLast Update
0023379mantisbtbugtrackerpublic2017-10-01 14:55
Reportermathieu.soum Assigned Toatrol  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
PlatformMozilla FirefoxOSWindowsOS Version10
Product Version2.0.0 
Summary0023379: Bad quote escaping with French locale
Description

The quotes (single and double) are escaped but the "escaping" backslash in the summary and description of issues but are not removed when showing the string afterwards.
I noticed it a few versions ago and it is still not fixed in the v2.0.0.
I am using the French locale.

For example, if I have a bug summary like :

Le résumé d'un "problème".
It will be stored in the DB and show in the bug list as follows:
Le résumé d\'un \"problème\".
Then when editing this issue, the text show in the Summary field will still have the backslashes like:
Le résumé d\'un \"problème\".
Let's say I change the description and save the modifications, even more backslashes will appear in the DB and shown in the bug list like:
Le résumé d\\'un \\"problème\\".
And so forth.

I understand the necessity of escaping the quotes but it make the texts hard to read very quickly.
I have not updated to the latest version yet. Did I miss a report for this bug ? Is it already fixed in a newer version than the v2.0.0 ?
If not, the texts with quotes should be shown and be editable without any backslashes added to them.

TagsNo tags attached.

Activities

atrol

atrol

2017-09-20 11:02

developer   ~0057766

Run admin/check/index.php
I assume you will get some errors and/warnings, some of them related to PHP settings.

mathieu.soum,

This is not a bug or feature request for MantisBT (you are asking for help on how to configure the system). I am therefore resolving this issue as "no change required".

Please use the forums to get support on customizing and using MantisBT (refer to http://www.mantisbt.org/support.php for links and further details).

Feel free to reopen the issue if you still get the problem after a) having fixed your PHP settings and b) using latest stable version (2.6.0 at the moment)