custom fields in biblio records gone after drupal upgrade
| Project: | Bibliography Module |
| Version: | 5.x-1.16 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Not sure how to categorize this issue.
I added a custom field to my biblio content ("research area").
When I upgraded from Drupal 5.7 to 5.8, this custom field disappeared (and views based on it no longer worked). I assumed I had done something wrong, and I put the field back in, and redid the content for those records.
When I upgraded to Drupal 5.9 this happened again.
I noticed at that time that there was a new Biblio module (1.16). I installed it and ran update.php. [no effect on the custom field issue]
The logs don't show anything relevant.
In the Filter section of the Views module, the field which used to be used for choose the value of the custom field (' Include or exclude nodes of the selected types' ) now has an empty popup.
I'm also using modules Biblio Views and Biblio Normalize.
I know Biblio is not guaranteed to play well with Views, but everything was working ok. Maybe some table gets clobbered or reset to some default in the upgrade? Is there a way to restore just that table, or the column containing the custom field?
#1
I thought of not adding a custom field to Biblio content type next time, but using built-in fields such as
biblio_fields.biblio_research_notes
biblio_fields.biblio_keywords
... and then writing code to pull out fields without relying on Views (as we've discussed).
I went into 'edit content type' to see more about them, and can't find details ("There are no fields configured for this content type.")(?)
The biblio tables are there & contain the data, except apparently for my custom Research Area field - but I don't see where that would be stored if it still exists. Maybe in one of the node tables? I poked around in those, don't see it.
#2
Looking for what the Drupal upgrade did to the custom field I'd added to the Biblio module.
sdiff -s post_upgrade.sql pre_upgrade.sql :
{ bunch of stuff }
> field_research_area_value longtext,
> INSERT INTO content_type_biblio VALUES (159,159,'industrial') etc.
So, I learn that a custom field added to the Biblio content type is stored in a core Drupal table, not a Biblio table.
mysql> select * from content_type_biblio; --> Empty set
I guess the upgrade overwrites that table, which is apparently created by 'core'.
However, *all* such tables are empty (content_type_page, etc.), even though pages, etc., were not affected by the upgrade. So not sure what this signifies.
Anyway, looks like I'll have to re-do the custom field and its content.
Is there a better approach? This will pop up in Drupal 6.
Views will filter by Taxonomy but I don't see a way to apply Taxonomy to a Biblio record.
Could use the built-in keywords field but I want the custom field (e.g., choice of Research Area), to be a pop-up, to save work on data entry, and prevent typos.
Thanks for any advice.
#3
From now on I will do a separate-table dump of content_type_biblio, so I can restore it more easily.
Could you point out what [ keys?] link that table to the biblio tables?
I can recreate the content_type_biblio table and insert the values from the *.sql backup, but that doesn't cause them to appear as 'set' in the biblio records, only as yet-to-be-set in the pop-up for the field in the record.
#4
I'm still in vacation mode for another couple of weeks. I know this doesn't help, but I just wanted to let you know I didn't get hit by a bus or anything :-)
Ron.