MantisBT - v3.0 Release
View Issue Details
0001305v3.0 Release[All Projects] Generalpublic2013-04-26 05:162013-08-28 11:17
ReporterGQQSER 
Assigned Tocaseydk 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version3.0.0 
Summary0001305: back slash added at each time parenthesis added
DescriptionIn the task description and in the task logs, each instance of " will cause a \ to be entered before it. So if I were to type 38", it would appear 38\" everywhere.
Sometimes there are multiple backslashes such as 38\\\"
Additional InformationThis anomaly happens whether I type or cut & paste.
TagsNo tags attached.
Attached Files

Notes
(0002904)
caseydk   
2013-05-22 23:06   
Resolved: https://github.com/web2project/web2project/commit/df02a7ad3589a07ee97c74c7801145e733dd28b2
(0002907)
GQQSER   
2013-05-23 14:39   
I am still getting the hash marks after I have applied the fix. I tried clearing my cache, I updated the file several times and I still have this issue. There maybe some other reason I am not familiar with.
(0002918)
caseydk   
2013-06-01 21:32   
What version of PHP are you using? Do you have magic quotes or something similar enabled?

Also, my fix will not undo previously modified data.. just prevent it from being modified in the future.
(0002925)
GQQSER   
2013-06-02 06:40   
Apache version 2.2.24
PHP version 5.2.17
MySQL version 5.5.31-log
Architecture x86_64
Operating system linux

You were right, problem was resolved had this in my php.ini file:

; Magic quotes
magic_quotes_gpc =on ; magic quotes for incoming GET/POST/Cookie data
magic_quotes_runtime =Off ; magic quotes for runtime-generated data, e.g. data from SQL, from exec(), etc.
magic_quotes_sybase =Off ; Use Sybase-style magic quotes (escape ' with '' instead of \')

Problem resolved the first time. Sometimes I feel like caveman beating on a stone tablet. Sorry for the doubting.
(0002926)
caseydk   
2013-06-02 17:57   
Absolutely no worries. It took me a while to come up with that possibility, so it was a good reminder of what else could be out there that I should watch for. :)

Issue History
2013-04-26 05:16GQQSERNew Issue
2013-05-22 23:06caseydkNote Added: 0002904
2013-05-22 23:06caseydkStatusnew => resolved
2013-05-22 23:06caseydkResolutionopen => fixed
2013-05-22 23:06caseydkAssigned To => caseydk
2013-05-23 14:39GQQSERNote Added: 0002907
2013-05-23 14:39GQQSERStatusresolved => feedback
2013-05-23 14:39GQQSERResolutionfixed => reopened
2013-06-01 21:32caseydkNote Added: 0002918
2013-06-02 06:40GQQSERNote Added: 0002925
2013-06-02 17:57caseydkNote Added: 0002926
2013-06-02 17:57caseydkStatusfeedback => resolved
2013-06-02 17:57caseydkResolutionreopened => fixed
2013-08-28 11:14caseydkFixed in Version => 3.0.0
2013-08-28 11:17caseydkStatusresolved => closed