About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
changelog

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
changelog [2020/05/28 19:33] – [Release 7.0 - currently in development] demiankatzchangelog [2020/06/04 17:35] – [Release 7.0 - coming 7/20/2020] demiankatz
Line 3: Line 3:
 // When adding a new release, see the [[changelog:release_checklist|release checklist]]. // // When adding a new release, see the [[changelog:release_checklist|release checklist]]. //
  
-===== Release 7.0 - currently in development =====+===== Release 7.0 - coming 7/20/2020 =====
  
 New features: New features:
Line 11: Line 11:
   * ArchivesSpace integration (support for ingesting Dublin Core records harvested from ArchivesSpace over OAI-PMH; see [[https://github.com/vufind-org/vufind/pull/1623|pull request #1623]]).   * ArchivesSpace integration (support for ingesting Dublin Core records harvested from ArchivesSpace over OAI-PMH; see [[https://github.com/vufind-org/vufind/pull/1623|pull request #1623]]).
   * When using the optional link shortener feature, you can now configure how shortlinks redirect to full URLs (HTML-based, header-based, or conditional URL-length-based redirection). See [[https://github.com/vufind-org/vufind/pull/1533|pull request #1533]].   * When using the optional link shortener feature, you can now configure how shortlinks redirect to full URLs (HTML-based, header-based, or conditional URL-length-based redirection). See [[https://github.com/vufind-org/vufind/pull/1533|pull request #1533]].
 +  * VuFind's integration with EBSCO Discovery Service has been significantly improved, with a large number of bug fixes.
   * New [[development:plugins:view_helpers|view helpers]] ("slot" and "parentTemplate" / "templatePath") make it easier to extend and customize core templates. See [[https://github.com/vufind-org/vufind/pull/1454|pull request #1454]] and [[https://github.com/vufind-org/vufind/pull/1458|pull request #1458]] for details.   * New [[development:plugins:view_helpers|view helpers]] ("slot" and "parentTemplate" / "templatePath") make it easier to extend and customize core templates. See [[https://github.com/vufind-org/vufind/pull/1454|pull request #1454]] and [[https://github.com/vufind-org/vufind/pull/1458|pull request #1458]] for details.
   * Custom [[configuration:feedback|Feedback Forms]] now support help text both before and after form elements through new pre/post help configuration settings.   * Custom [[configuration:feedback|Feedback Forms]] now support help text both before and after form elements through new pre/post help configuration settings.
Line 30: Line 31:
   * :!: Zend Framework has become Laminas; this upgrade has caused significant changes throughout the code because of class and package name changes. You should update your local code to match. See [[https://github.com/vufind-org/vufind/pull/1537/|pull request #1537]] for details.   * :!: Zend Framework has become Laminas; this upgrade has caused significant changes throughout the code because of class and package name changes. You should update your local code to match. See [[https://github.com/vufind-org/vufind/pull/1537/|pull request #1537]] for details.
   * :!: The Laminas\Console component has been deprecated, so all command line tools have been migrated to use Symfony\Console instead; see [[https://github.com/vufind-org/vufind/pull/1571|pull request #1571]] and the [[https://blog.library.villanova.edu/2020/04/23/vufind-moving-from-laminasconsole-to-symfonyconsole/|console migration blog post]] for more details.   * :!: The Laminas\Console component has been deprecated, so all command line tools have been migrated to use Symfony\Console instead; see [[https://github.com/vufind-org/vufind/pull/1571|pull request #1571]] and the [[https://blog.library.villanova.edu/2020/04/23/vufind-moving-from-laminasconsole-to-symfonyconsole/|console migration blog post]] for more details.
 +  * :!: VuFind's default Solr port has changed from 8080 to 8983, to better reflect Solr best practices and to reduce port conflicts with other applications; it can easily be [[administration:security#changing_the_solr_port_number|changed back]] as needed.
   * :!: VuFind's session handler code has been significantly refactored to improve extensibility and testability; see [[https://github.com/vufind-org/vufind/pull/1506|pull request #1506]] for details. If you have built a custom session handler, it will likely need to be adjusted; otherwise, this should not impact you.   * :!: VuFind's session handler code has been significantly refactored to improve extensibility and testability; see [[https://github.com/vufind-org/vufind/pull/1506|pull request #1506]] for details. If you have built a custom session handler, it will likely need to be adjusted; otherwise, this should not impact you.
   * :!: VuFind's jQuery version has been upgraded from 2.1.1 to 3.5.1; if you have custom jQuery code, you should double-check its compatibility.   * :!: VuFind's jQuery version has been upgraded from 2.1.1 to 3.5.1; if you have custom jQuery code, you should double-check its compatibility.
Line 39: Line 41:
   * :!: The way feedback forms do text translation has been refactored; if you have customized this code, you may need to adjust to match. See [[https://github.com/vufind-org/vufind/pull/1565|pull request #1565]].   * :!: The way feedback forms do text translation has been refactored; if you have customized this code, you may need to adjust to match. See [[https://github.com/vufind-org/vufind/pull/1565|pull request #1565]].
   * :!: Because score values are never used in core code (except when dumped out in non-MARC staff view tabs), the default field list retrieved from Solr has been changed from "*,score" to simply "*". There is now a default_record_fields setting in searches.ini (and other equivalent Solr backend configurations) which can be used to customize the field list. See [[https://github.com/vufind-org/vufind/pull/1568/files|pull request #1568]] for details.   * :!: Because score values are never used in core code (except when dumped out in non-MARC staff view tabs), the default field list retrieved from Solr has been changed from "*,score" to simply "*". There is now a default_record_fields setting in searches.ini (and other equivalent Solr backend configurations) which can be used to customize the field list. See [[https://github.com/vufind-org/vufind/pull/1568/files|pull request #1568]] for details.
 +  * The EBSCO Discovery Service integration now uses POST instead of GET for search API requests; the legacy GET behavior can still be accessed through an EDS.ini setting. See [[https://github.com/vufind-org/vufind/pull/1627|pull request #1627]] for details.
   * The \VuFind\RecordTab\TabManager::zendConfig property has been renamed to legacyConfig to prevent Laminas-related confusion; because this property is only used for accessing obsolete configuration settings, the impact of this change is expected to be minimal... but if you have customized the TabManager, you should check for issues. See [[https://github.com/vufind-org/vufind/commit/46e10504b90da88d0b4673a085b19941088f23b4|this commit]] for details.   * The \VuFind\RecordTab\TabManager::zendConfig property has been renamed to legacyConfig to prevent Laminas-related confusion; because this property is only used for accessing obsolete configuration settings, the impact of this change is expected to be minimal... but if you have customized the TabManager, you should check for issues. See [[https://github.com/vufind-org/vufind/commit/46e10504b90da88d0b4673a085b19941088f23b4|this commit]] for details.
  
changelog.txt · Last modified: 2024/07/08 19:37 by demiankatz