library 8.x-1.0-beta1

Bug fixes
New features

This release includes numerous bugfixes and removes several hardcoded placeholders, so it should be possible to now work more flexibly with the module.

The code quality is still mediocre. Dependency injection is not used consistently, unit tests are missing and the field widget is especially ugly in its post-processing. Bulk updates could also be more user friendly (see the issue queue).

library 8.x-1.0-alpha3

Bug fixes

Fixes problems with the form widget, this works reliably now and only has the hardcoded dependency of the library_item naming (for now).

library 8.x-1.0-alpha2

Bug fixes
New features

Basic port completed, significant UX issues remain to be fixed in the widgets in use. General library operations are working and usable.

library 8.x-1.0-alpha1

This release provides a generally functional and working state of the library module.

Remaining known issues:

library 7.x-1.0-alpha1

Bug fixes

This release reflects the work done in #973574 on a port of this module to Drupal 7.

The module has been tested, and no loss of data should occur but no external feedback has been received yet, therefore it is alpha1 instead of beta1 or rc1.

library 6.x-2.x-dev

New features

This version of the library module removes the patron sub-module. Instead, patrons are now simple Drupal users. This both simplifies the module code and should make this module more intuitive to use. This will be the supported/recommended branch in the future.

Also added in this release:
A history tab for each user with their past library activity and a history tab for each library item with who/when library actions were performed.

For Those Upgrading:
Former users of the library module will not be able to update unless they are using the "associate library patrons with Drupal users" option and have users associated with all patrons. If you would like to upgrade to this version but didn't use the user option, you should be able to check "associate with users" (available in Library Settings), create matching user accounts with the same email addresses as your patrons, and then save the patron nodes. All patrons must have an associated user before the update will run.

Subscribe with RSS Subscribe to Releases for Library