Terms with ampersand are not converted to term-id when sent as arguments

Looks like your patch is missing another newline at the end.
I could apply it using the patch utility, but not with git apply.
Rerolled

this patch fixed this issue for me

Is this issue related to #672606: Hyphens and forward slashes (-/) break Views contextual filters? It would be great if this patch killed two issues.

Edit: sorry, didn't mean to reference the same issue...

Just curious, will this patch be in the next Views release?

If you select the option to convert spaces in term names to hyphens this patch is no longer effective. Investigating this now, I'll post a patch if I can figure it out.

Hello meeli,

Selecting option "convert spaces in term names to hyphens" did not work for me when I pass the argument through a views pane context and the passed name come from a term reference field value. The ampersand contained in the term name is still "&".

The patch supplied by jeffschuler worked for me (thanks for it!).

I think that the decode_entities should also applied when the the option "convert spaces in term names to hyphens" because of other special characters that could be to convert like "é", "ç", "ô".
Do you see a case where that could not work by applying the decode_entities in this case?

Thanks for the patch!

@jyraya, @meeli: I cannot find the option Convert spaces in term names to hyphens, is this in Panels or Views?

I did find the Transform dashes in URL to spaces in term name filter values option in the Views' contextual filter dialog window. The patch from #6 does not take this option into account, it only decodes entities if the transform option has not been set.

Attached patch decodes entities in both cases, please review and set RTBC if all is ok!

#13 worked for me. thanks!

Just hit this myself - I was using a term contextual filter both on a page view and a block on the same page view. This issue only affected the block view and ONLY because it had an exposed filter and did a keyword search via ajax. The search worked fine in preview but not on the actual view page, and the term correctly converted with an ampersand in it to get the base category contextual filter on the block, just not with the ajax exposed filter keyword search.

Patch in #13 also worked for me, count me in as another happy reviewed-and-tested-it community member.

I'm having trouble with getting this to work. Could someone who's successfully tested post the term names they've tested with? It seems to me that this still doesn't fix the issue. It looks like it's decoding entities in the argument, but not in the td.name, which is what we need, right? I have terms like "Arts & Humanities" which don't match with the

Playing around with the query, I came up with this:

       if ($transform) {
          $query->where("replace(replace(td.name, ' & ', '-'), ' ', '-') = :name", array(':name' => decode_entities($argument)));
        }

but that seems hacky and probably not valid behavior for every case, maybe? What I (we?) really need is to totally clean the string like in pathauto_cleanstring or ctools_cleanstring and at that point using merlinofchaos's advice is probably simpler (and what I'll most likely do). Can someone give me a sanity check here? If it looks valid, I can set it up for both cases and submit a new patch.

We've recently switched our testing from the old qa.drupal.org to DrupalCI. Because of a bug in the new system, #2623840: Views (D7) patches not being tested, older patches must be re-uploaded. On re-uploading the patch, please set the status to "Needs Review" so that the test bot will add it to its queue.

If all tests pass, change the Status back to "Reviewed & tested by the community". We'll most likely commit the patch immediately without having to go through another round of peer review.

We apologize for the trouble, and appreciate your patience.

Re-uploading the patch from #13.

Set status back to RTBC according to the request in #17.

Thanks for the patch. Just to feedback on this, I have tried the patch on #18, but though it fixes the problem on the 2nd page, it broke again on the 3rd page. We're using Views 7.x-3.11.

Hey,

I've got the same problem described in #3.
I have a page /content/Internet-&-Media where the "Internet & Media" is the taxonomy term name.
A message appears "Page not found" (generated by Views module). Also, I've added Override title option in the contextual filter and the title shows only the part of the title - "Internet".

The /content/Internet-%26-Media path works fine. I'm using Views 7.x-3.14.

If you need additional info - just ping me.

Sounds like this needs more work, maybe a test would help too?

Hi, after 2 years not correct working still..anyone have a solution please?

I had assumed (obviously incorrectly) that views would treat this like pathauto does, and sluggify a term like "Anthropology & Sociology" into "anthropology-sociology"

Hi Safetypin, I had the same assumption...but no solution yet.
Anyone have a solution please?
greetings, Martijn