8000 Releases · GetDKAN/dkan · GitHub
[go: up one dir, main page]

Skip to content

Releases: GetDKAN/dkan

2.21.2

01 Oct 20:19
c8bcdfd

Choose a tag to compare

Note

This release fixes a problem reported in #4531; that the permissions to access the datasets admin page were too permissive. The change will not be automatically applied; see the section below "View Update Instructions" for how to import the new config.

What's Changed

  • Improve some docs about the Drush commands by @dafeder in #4560
  • Restrict view perms, remove routing perms by @dafeder in #4563
  • Additional decoupling of DKAN from JSON Form Widget in tests by @dafeder in #4567

View update instructions

The changes to the datasets admin view are not automatically applied, to avoid blowing away any customizations. If you are comfortable replacing the default datasets admin view at admin/dkan/datasets, use either one of the following methods:

  • Run the drush command drush cim --partial --source=modules/contrib/dkan/modules/metastore/modules/metastore_admin/config/install -y
  • Use the configuration sync UI:
    1. Open the file modules/metastore/modules/metastore_admin/config/install/views.view.dkan_dataset_content.yml
    2. Copy the full contents
    3. Navigate to admin/config/development/configuration/single/import
    4. Set "Configuration type" to "View"
    5. Paste the contents of the yml file
    6. Click "Import"

Full Changelog: 2.21.1...2.21.2

2.21.1

22 Sep 18:18
735cf03

Choose a tag to compare

What's Changed

Full Changelog: 2.21.0...2.21.1

2.21.0

10 Sep 18:22
d3ceee2

Choose a tag to compare

Important

This release introduces several breaking changes to composer dependencies and the datastore API. See below for upgrade instructions.

Upgrade guide

  1. composer.json: Ensure that your project root composer.json includes npm-asset/select2 and oomphinc/composer-installers-extender in the require section, and asset-packagist in the repositories section. See #4546 and the select2 readme for more information, or see this project template for an example. If you omit the npm-asset/select2 dependency, your project should still build, but your metadata forms may break.
  2. select2: You must require the development branch of select2 at a more recent commit than select2/select2#6332. There is unfortunately no stable release that is compatible with current versions of Drupal. This means that projects using DKAN must have minimum stability of dev in their composer files (or else omit the select2 library dependency and avoid using select2 on your forms).
  3. API change: Using "limit": 0 in a datastore query to get around the row limit in the datastore query endpoints will no longer work, and will produce a JSON validation error. Please update any frontend or third-party code. The only way to download a full result set from the datastore, without being affected by the row limit setting, is to use one of the download endpoints and consume the entire result as a CSV.
  4. Config: If you save your project configuration to code, be sure to capture the changes to core.entity_form_display.node.data.default.yml as there has been an update to the JSON form plugin.

What's Changed

Full Changelog: 2.20.9...2.21.0

2.20.9

15 Aug 19:25
93a4b0b

Choose a tag to compare

Important

As of Drupal 8.2.0, modules no longer require REST-specific permissions. This update begins the transition from a separate permission for API use to relying on the Drupal content authorship permissions. The permission post put delete datasets through the api is deprecated. All API actions now require the same permissions needed to accomplish equivalent things in the Drupal UI. They will, for now, also respect the old "post put..." permission for backward compatibility, but we will remove this in a later release.

Please be advised that you should update the Data node permissions on your data publisher role(s) accordingly.

What's Changed

What's Fixed

  • Override file access to allow access to remote files for UploadAndLink by @beeyayjay in #4536

2.20.8

11 Aug 18:13
8d8b7d9

Choose a tag to compare

Note

This update adds a new configuration for the DKAN MySQL Importer module: "Disable strict mode for creating/altering MySQL tables". Previously the module would always attempt to disable innodb_strict_mode before creating or altering a datastore table. This is sometimes needed for edge cases where the data resource may exceed the header size limit. See #4505.
If a mysql user lacks the necessary permissions to disable strict mode, however, this will cause errors on table creation. If you do not need strict mode to be disabled or do not have the necessary permission, you should not be disabling innodb_strict_mode. After upgrading, visit /admin/dkan/datastore/mysql_import and uncheck the "Disable strict mode for creating/altering MySQL tables" option. (On new installations, it will be unchecked by default.)

What's Changed

  • Allow null on addDistributionInfo in DatastoreInfo by @janette in #4509
  • Migrate from code climate to qlty by @dafeder in #4513
  • Strict mode opt-in for MySQL importer by @dafeder in #4512
  • Split dashboard title search terms into multiple conditions in query to get accurate results by @kaise-lafrai in #4520
  • Remove flaky test by @dafeder in #4522
  • Isolate all DKAN logic in JSON Form widget to plugin file by @dafeder in #4486
  • Test coverage for API delete, and for unauthorized request by @dafeder in #4523

What's Fixed

  • Query Schema updates to throw json schema validation errors if any of the conditions are not met. @kaise-lafrai #4528

2.20.7

23 Jun 19:42
671ea68

Choose a tag to compare

Note

This release contains updates to the administration views, if you have not customized these views you can pull in the updates with
drush cim --partial --source=modules/contrib/dkan/modules/metastore/modules/metastore_admin/config/install -y.

What's New

  • Add entity operations on DKAN content views by @paul-m in #4499 #4502
  • Add drush command to find the dataset corresponding to a datastore table by @rovcase in #4399

What's Changed

What's Fixed

  • Update metastore_search to ensure only DKAN content is processed by @paul-m in #4471
  • Fix the dictionaryEnforcer by passing both the resource ID and version by @janette in #4485

2.20.6

13 May 22:10
c049ba9

Choose a tag to compare

This release contains several significant improvements to the json_form_widget module, which is used to render the dataset and other metadata forms from JSON schemas. Arrays of fields or items can now be re-ordered, and individual fields/properties can also be given weights so that their order on the form does not need to reflect their order in the JSON schema document.

This is the result of quite a bit of trial and error with the Drupal Forms API. There is already one known issue (#4489); please submit any additional findings to the DKAN issue queue or discussions.

Note

(Updated 8/19/25) #4427 changes the namespacing for certain key Harvest classes. If you have custom code that depends on anything in the Harvest namespace, it will need to be changed to Drupal\harvest.

What's New

What's Changed

Full Changelog: 2.20.5...2.20.6

2.20.5

15 Apr 14:21
0011dbd

Choose a tag to compare

Note

Module dependencies have changed. If you have custom services that depend on the harvest or datastore modules, but don't have those modules explicitly declared as dependencies of your module, your services may break. Make sure to add dkan:harvest and/or dkan:datastore to your module's .info.yml file.

What's Fixed

What's Changed

Full Changelog: 2.20.4...2.20.5

2.20.4

27 Mar 13:12
4774cfe

Choose a tag to compare

What's Changed

Full Changelog: 2.20.3...2.20.4

2.20.3

13 Mar 20:42
859f2d1

Choose a tag to compare

This release brings, along with other minor fixes, full PHP 8.4 support to DKAN.

What's Changed

Full Changelog: 2.20.2...2.20.3

0