Stripslashes: why?

I have a problem: if I introduce a backslash ’\’ in the document content, it does not appear in the outputted HTML page. If I want to output a backslash, I have to quote it ’\\’.

The cause is a "stripslashes" call in document.parser.class.inc.php (there is only one stripslashes, in MODx 0.9.1). If I remove it, everything looks fine.

My question is: what is the purpose of that "stripslashes" in the parser? Can I safely remove it?
Thanks,
Luca

Just FYI, I posted this in the bugtracker already a while ago. See http://modxcms.com/bugs/task/181

Thanks Mitch, that’s exactly my problem. As I can see, you didn’t get answers in the bug tracker, so the question remains if this is a "feature" (and why) or a bug

Quote from: Commodore64 at Apr 26, 2006, 11:55 AM

Thanks Mitch, that’s exactly my problem. As I can see, you didn’t get answers in the bug tracker, so the question remains if this is a "feature" (and why) or a bug

Bug or feature, it should be addressed. I’ll look into it now that I am aware of it.

Great I’ll post a LaTeX plugin when this situation is clarified

Hi guys,

the same problem described by Commodore64 persist here. I use the 0.9.2.1 Rev 1005. This BUG can be reproduced any time.

Thanx,

Chris

Yep, I can confirm that too

MODx 0.9.2.1 (rev 1005)

For example here:
http://www.frozenminds.com/disable-sessionid.html (last code block)

A much better example is here:
http://www.frozenminds.com/slash-test.html

I have used following code in my docment:

(You can see the results on the page above)

BTW: I have also updated the bug report http://modxcms.com/bugs/task/181

Boby

If the comment says "fixed in rev#1247", it isn’t particularly helpful to state that it is present in rev 1005.

The Rev number is the real version number. Yes, that means there have been a few hundred updates since 0.9.2.1.

That said, given that you’ve raised the issue from the dead, I *can* confirm that it is present in rev 1371. That isn’t the absolute latest 0.9.5 beta, but is post-parser-revert (1247 probably had the experimental parser). I’ll check the latest rev later and update the bugtracker accordingly unless someone beats me to it.

I found this problem to still be in MODx 0.9.5 public beta.

So, I’ve done a bit of testing and put in the fix to SVN to remove the stripslashes() call. From my testing so far, it isn’t causing any adverse effects by not having it there. (bugtracker has been updated)

Quote from: garryn at Sep 13, 2006, 03:43 PM

I found this problem to still be in MODx 0.9.5 public beta.

So, I’ve done a bit of testing and put in the fix to SVN to remove the stripslashes() call. From my testing so far, it isn’t causing any adverse effects by not having it there. (bugtracker has been updated)

Fix committed in revision 1416, which is on it’s way through sanity checks before hopefully becoming the second public beta release of 0.9.5. More soon.