The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Through some trial and error I found that the Dec 22 release of References is causing all ampersands in select lists throughout my site (using User Reference) to show as & instead of "&". I myself am not sure what could be causing this, but I know for a fact that it's the newest version of the References module. I ran tests on fresh installs of drupal 7.10 with a previous version of References and everything works fine. As soon as I install the newer Dec 22 version 7.x-2.0 all ampersands in select lists turn to &. Please let me know if you need any information to fix this.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | references-exposed_filters-1391814-5.patch | 4.14 KB | yched |
| #3 | references-1391814-3-2.0.patch | 797 bytes | boobaa |
| #3 | references-1391814-3-2.x.patch | 659 bytes | boobaa |
| #1 | reference-widgets-HTML-entities-1391814.patch | 2.13 KB | yched |
Comments
Comment #0.0
brettJames_ commentedCorrection: Only select lists using User Reference.
Comment #1
yched commentedRight, I introduced that regression in #1155946: "radios / checkboxes" widget could support HTML tags (img...) coming from views.
I committed the attached patch in 7.0-2.x, which should fix this.
Comment #3
boobaaDon't know if it's OK to reopen this issue, but my one seems to be related.
If I have an exposed filter of referenced nodes, I have the filter's
<select>box filled with<span class="views-field views-field-title"> <span class="field-content"><a href="/node/1">Title 1</a></span> </span>and alike (instead of the expectedTitle 1).Attached patches solves this issue, but I must admit that I don't know if they introduce new/reopen old issues. (Attaching patches for both references-7.x-2.0 and references-7.x-2.x-as-of-now.)
Comment #5
yched commented@Boobaa : Correct. Views uses this same list of options to display checkboxes (in the filter settings form) and select dropdowns (in exposed filters). Problem is, those two form elements have completely different requirements in terms of sanitization.
Attached patch is the correct fix - committed to 2.x.
(side note : patch also fixes a name mismatch between the function names in node_reference and user_reference modules. Update function included, so that the views info cache is rebuilt and catches the change)
Comment #6
yched commentedCreated #1436598: Sanitation dilemma for 'options_callback' in Views issue queue.
Comment #7
00trav commentedEncountered this problem when upgrading to 2.0. Posting here for others that run into this problem.
Fixed by upgraded to latest Dev version (2012-Feb-11).
Comment #8.0
(not verified) commentedFixed a couple of typos.