Closed (duplicate)
Project:
Location
Version:
5.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
9 Apr 2007 at 18:10 UTC
Updated:
13 Jan 2018 at 17:26 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedHas anyone got any further information on this issue?
Mark
Comment #2
Anonymous (not verified) commentedHas anyone got any further information about this at all?
Mark
Comment #3
niklp commentedMark, this sounds like a theming issue - you're saying that the View display is different than the node display.
I suggest that you use the Views Theming wizard to show what fields are being used in your view, and the devel module's node render tab (via the node view) to show what the node display is rendering - perhaps then you can answer your own question; it would appear that the data is there, but different "folks" are using different bits of it for different things...
HTH
Comment #4
Anonymous (not verified) commentedThis is just what I needed. I can now see that the Province field is overridden by the phptemplate_views_handle_field_location_province function in my view. So if I can get that into my node view the problem is solved.
Thanks,
Mark
Comment #5
catchhttp://drupal.org/node/115323 was duplicate.
Comment #6
catchack.
Comment #7
scott.mclewin commentedsubscribing. Showing full province names would be a most helpful fix. Also, feeding the full province name into the Drupal search indexer rather than the province code would be beneficial.
Comment #8
catchActually, this is the duplicate, and it's not only a theme issue.
Comment #9
koredeola commentedthis is one solution that i have used
assuming you already have the information you need from a query in the variable $locations_and_counts