I'm new to bug reports. I *think* this is a bug but unsure if issue is code or user interface.
Upgraded from v1.8 to v.1.15 (I think. I uninstalled & removed old version, but Drupal report shows old version).

Issue: content entered in a field is not showing up in the database, at least not in expected fields. Possible disconnect between user interface and database for different record types.

Gory details on forum (http://drupal.org/node/70562) but basically:
Created two Biblio records (a report and a conference paper). Made a View (name, year, and secondary title).
[Secondary Title because Biblio:Title does not show up in the View field popup, although it shows up on the web page where you create Biblio records.]
The resulting View
-provides no label for the Secondary Title column
-does not display the (secondary?) title for one of the publications, which I *did* enter on the web page
The other record is properly displayed (all fields).

I queried the database (select * from biblio).
For the properly displayed record, the title appears in biblio_coins, but biblio_secondary_title actually contains the proceedings name.
For the 'problem' record (missing a title), title info is in biblio_coins field, but not in biblio_secondary_title.
Maybe upgrade didn't work - or fields are mislabeled on the web page? Or some problem with database input?

Comments

rjerome’s picture

rjerome commented

Hi,

First let me say that this is the correct place to post issue reports. I monitor these reports, but I did not see your previous posts at (http://drupal.org/node/70562).

With regards to your apparent version discrepancy... I believe you said that you "moved" the old biblio directory but unless you moved it completely out of the "Drupal" directory tree, Drupal will still find it and depending on the order it finds them, it may still be using the old version.

Next, it sounds to me like you are using "Views" to create your output. I should tell you that the views support in biblio is quite limited at this time and doesn't include any "styling", the 6.x version should have better "views" capabilities. Any of the output you would see from a standard installation is done internally, not using "Views". The bottom line is I wouldn't recommend using views at this time.

You can create your own style formats by copying one of the "style" files in the biblio directory. A good example might be the "bbilio_style.ieee.inc" file. You would change any references to ieee to what ever your style is called, and rename the file also, then the UI will detect the new style and display it as an option on the admin page.

With regards to your database issues... The field names in the biblio database table do not necessarily correspond to the field labels on the input form. For example, the secondary title field can contain the Journal Title or Book Title depending on the publication type. The mapping is done through the biblio_fields, biblio_type_details and biblio_types tables. The title is stored in the node:Title field since biblio is an extension of the node type.

Hope this helps but as I said earlier, the views support is not the greatest so if this is a must have feature I'm afraid you will have to wait for a newer release.

Ron.

Anonymous’s picture

Anonymous (not verified) commented

Thank you for your time.

>unless you moved it completely out of the "Drupal" directory tree, Drupal ... may still be using the old version.

Right you are - fixed, now the new version shows up in Modules.

I'll work on the other items now.

bekasu’s picture

bekasu commented
Status: Active » Closed (fixed)

Marking issue closed.