Closed (fixed)
Project:
Views (for Drupal 7)
Version:
5.x-1.4-2rc1
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
20 Dec 2006 at 16:37 UTC
Updated:
30 Jan 2007 at 04:47 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Permanently Undecided commentedI can confirm this and also that the fix suggested works perfectly.
Comment #2
Anonymous (not verified) commentedAnother confirmation. It solved my problem http://drupal.org/node/105193
Thanks for the info.
Comment #3
dodorama commentedjust to rise attention on this bug
Comment #4
Permanently Undecided commentedHere's a patch that fixes this.
What was the problem?
Basically, the Drupal way is to name css identifiers with hyphens (-) and to never use underscores (_), even though according to the w3.org specification you can use both: .
In order to follow the Drupal's css identifier naming guidelines, all the names were sanitized using the function views_css_safe() that substitutes underscores with hyphens. However, instead of doing this for css class names only, this was also done for actual field names, which caused the bug.
My patch adds a new variable that holds the sanitized field name to use with css classes, and keeps the correct, unsanitized field name to use with, obviously, fields.
Comment #5
merlinofchaos commentedThanks for the patch, PU! Applied. Sorry about the delay, the holidays have had me quite busy.
Comment #6
(not verified) commented