#1053 closed defect (bug) (fixed)
Slashes added to double-quotes in < pre > found in post content
| Reported by: | dsandler | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | General | Version: | 1.5 |
| Severity: | minor | Keywords: | |
| Cc: | Focuses: |
Description
Example post body (as entered in the admin pages, and verified by dumping the table in mysql):
<pre>'Singles' "Doubles"</pre>
As rendered on page (either in edit preview or on site itself):
<pre>'Singles' \"Doubles\"</pre>
Adding a call to stripslashes() to something like clean_pre() is the Wrong Thing To Do because it'll kill backslashes the user intended to be there.
A quick fix seems to involve adding a specific regexp for this case to clean_pre():
52a53
$text = str_replace('
"', '"', $text);
This seems to work for me, but I'm sure a more subtle fix is required to handle all cases.
Change History (5)
#3
@
22 years ago
- Summary Slashes added to double-quotes in <pre> found in post content → Slashes added to double-quotes in <pre> found in post content
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Eww---I didn't expect Mantis to emit the HTML un-escaped in bug lists and whatnot. Someone with Super Cool Privileges will probably have to clean up the bug report. Sorry!