Hi,

So I've made a custom view (in 6.x-2.0-beta3 as well as on our development site for 7.x-1.0-rc3 -- but we can just discuss 6x here, but the results seem to be the same)

So when adding the field 'Biblio Citation' -- there is the drop down menu for Style -- which seems to do nothing. I've outputted this as a page, and as preview, and also I have it embedded as a view in our 'Personal Page' content-type (for our librarians) -- but no matter what I toggle the Style to all I get back is either
1. if logged in - the style selected by the logged in user in their profile
or
2. unauthenticated users see the list as the system default styling.

This field seems to do nothing. Ideally what I was going to do was rewrite the query so I could grab the preferred style of the user that owns the node I was embedding the view on (using hook_views_pre_execute) -- in the meantime -- so I could get the output to display whatever the node owner's preferred style was, since this doesn't seem to be an option at the moment. However, there is nothing in the query that sets the style, and this dropdown doesn't seem to be doing anything.

Any ideas on this?

Comments

Frogtown’s picture

Also, just a follow up, wasn't sure if I should start another issue to ask this. I know the biblio style is stored in the $user array as biblio_user_style -- but I can't seem to find where this value is associated with the user in any of the tables -- where is this stored?

rjerome’s picture

Indeed, I'm surprised nobody noticed that before :-) It's fixed now.

D6: http://drupalcode.org/project/biblio.git/commit/63ad517
D7: http://drupalcode.org/project/biblio.git/commit/99f982f

WRT your other question, the user data is stored in the "users" table in the "data" column. It's stored as a serialized array.

Ron.

Frogtown’s picture

Thanks so much Ron. I always appreciate your promptness in replies and dedication to the module -- very cool.

David

liam morland’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

This version is no longer maintained. If this issue is still relevant to the Drupal 7 version, please re-open and provide details.