Hi there,

I have a site where the URL to editing a node can sometimes look like http://www.mysite.com/node/639/edit?destination=admin/content&language=fr

If I try to edit an autocomplete field of the node on this page, I see that the request sent back to the server looks like http://www.mysite.com/node_reference/autocomplete/node/slider/field_slid... (where 'test' is what I typed into the autocomplete field)

As you can see, Drupal removes the destination=.. parameter from the URL, but language=.. is kept in it, which results in no filtering occurring.

Anything that can be done about that? I wasn't able to find the place in the code where this is happening I'm afraid.

Cheers

Comments

disasm’s picture

disasm commented

I've tested this with a base 7.14 install. I was unable to reproduce the issue.

  1. Install Drupal 7.14
  2. Edit page content type
  3. Add field termref That's of type term reference with widget autocomplete term widget referencing "Tags" taxonomy terms
  4. Edit Terms for tagging
  5. Add bar
  6. Add abar
  7. Add foo
  8. Add bfoo
  9. Create New Page with tag bar
  10. Edit page using url: mysite/node/1/edit?destination=admin/content&language=fr
  11. Delete tag, start typing foo
  12. See terms foo and bfoo as options to select
disasm’s picture

disasm commented
Status: Active » Postponed (maintainer needs more info)

At the suggestion of Cottser, I re-ran the steps above with the enabling of the content translation module, and was not able to reproduce the issue still. One thing we noted was in your url, you have lang=fr as a parameter to the language string. I could not find anything in Drupal Core that treats languages that way. To do translation by url, it's usually mysite//rest/of/url.

Marking as postponed, needs more info.

dddave’s picture

dddave commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)
hhvardan’s picture

hhvardan commented
Issue summary: View changes
Status: Closed (cannot reproduce) » Active

I have the same issue ... did you find the solution?

Version: 7.14 » 7.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Status: Active » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.