Please see #158744: Autocomplete and Back Slash. This is the patch for Drupal 7. I wasn't sure if I should make another issue for this or not, so as you can see, I did.

Comments

Status: Needs review » Needs work

The last submitted patch failed testing.

callison’s picture

StatusFileSize
new513 bytes
callison’s picture

Status: Needs work » Needs review
StatusFileSize
new555 bytes

Take #2.

c960657’s picture

Status: Needs review » Active

I cannot reproduce this. I can auto-complete on terms containing backslashes without problems.

Which URLs are being called (you can see this using e.g. the Firebug console or the web server logs)? Which browser are you using?

callison’s picture

Status: Active » Needs review

I just tested this on Firefox, Chrome, and IE8 with the same problem all around. Here's the URL in the Apache log:

127.0.0.1 - - [01/Dec/2009:14:31:16 +0700] "GET /drupal-7/mpac/autocomplete/menu/%5C HTTP/1.1" 404 231

@c960657 - I'm not exactly sure what you mean by "auto-complete on terms containing backslashes". All I do to get this error is find an empty autocomplete field (Menu Path Autocomplete path field in this case), type in a backslash (\), and it pops up a dialog box saying there was a 404 error. Let me know if you still have trouble replicating this error. I get it every time.

mr.baileys’s picture

Status: Needs review » Postponed (maintainer needs more info)

I'm not exactly sure what you mean by "auto-complete on terms containing backslashes".

Auto-complete fields are used in numerous places in core, one of which is the taxonomy term auto-complete field. I tried reproducing the reported error but was also unable to do so, meaning it's possible that this is not a core bug, or is specific to your environment.

In order to review the patch we'll need to establish that this is indeed a bug in core, and not (for example) in the Menu Path Autocomplete module. Can you try and reproduce the error on a clean install without any contrib modules installed? If you still have an issue, please report back with the steps to reproduce this.

c960657’s picture

In #683736: Use db_like() where appropriate taxonomy_autocomplete() was changed to use db_like() to do proper escaping of special characters. This may have fixed this bug.

grendzy’s picture

Status: Postponed (maintainer needs more info) » Closed (duplicate)