biblio 6.x-1.0-beta6

This release has support for an upgrade path from the 5.x version and 6.x-beta5

Issues fixed since last beta...

• #260464: error while trying to import data
• #259177: Filter tab broken + wrong update status
• #261093: Problem with biblio_contributors field
• #260824: list view shows attachment which are not selected to be listed:
• #261109: Incompatible with node_clone?
• #261957: biblio.biblio_authors column
• #261123: Filtering by author shows strange filter name
• #261175: Publication Type specific fields not available, is this a not yet finished part of version 6?
• #260193: Author information
• #259473: Sort on full title, not just first letter

NOTE!!! Contrary to what the documentation says, if you are upgrading a 5.x database, you should leave the biblio module enabled during the upgrade.

The way I test upgrades (5.x to 6.x) is to make a backup of your entire 5.x schema and restore it to another schema name. For example, If I have a schema called D5 (which has all the usual drupal and biblio tables) and in settings.php the database line looks something like this...

$db_url = 'mysql://user:password@localhost/D5';

Then I would restore the drupal 5.x backup to a schema called "test". Now I would install Drupal 6.2 in another directory and get it all setup and working (including biblio) and then I would edit the settings.php file in the D6 installation and set the db_url to the newly created "test" schema that contains the 5.x tables restored from the backup. So the D6 db_url line would now be changed from this...

$db_url = 'mysql://user:password@localhost/D6';

to this...

$db_url = 'mysql://user:password@localhost/test';

and the update_access line should be set to true like this...

$update_free_access = TRUE;

Now you should immediately visit the update.php file on the D6 site. This should update the old D5 tables which you restored to the "test" schema to the D6 revision levels.

I hope that makes some sense.