apigee_devportal_kickstart 8.x-1.21

Downloads

Download apigee_devportal_kickstart-8.x-1.21.tar.gztar.gz 9.3 MB

MD5: a153cc4ec2529a68b134802b3c302cdf

SHA-1: 4758cf576205449643f4abea0cedc82171101812

SHA-256: a2a9e387a0cfd7522a07fc58afdf6664bef2774194008ec5707a9c4414debaf2

Download apigee_devportal_kickstart-8.x-1.21.zipzip 9.72 MB

MD5: 3b084e59d6e01d86b9156c9c647a66d6

SHA-1: 5399f552410ec008eb99b1fc1c787b5995424c4c

SHA-256: 2b8c5aaa3cbe26315e99169e5934a420036f494c8484e060a79a3fab0b645fa1

Release notes

Github milestone: 8.x-1.21

Changelog

Require the latest versions of apigee_edge (8.x-1.16) and apigee_api_catalog (8.x-2.4), via #432.
Drupal 9 compatibility fixes, via #432.
Added update hooks to simplify update to apigee_api_catalog 8.x-2.x, via #426 and #433.

Known Issues

If updating from 8.x-1.16 or a previous version: From version 8.x-1.17 "apigee_api_catalog" 8.x-2.x branch is required, so it will be updated from the 8.x-1.x branch. The update will try to recreate any custom fields that were added to the API Doc custom entity onto a new "API Doc" node bundle, migrate data, and delete all API Doc custom entities and definitions. It is highly recommended to test on a development environment before running it in production. It is necessary to run database updates if updating from a version before Apigee Developer Portal Kickstart 8.x-1.17.
After running database updates, the following manual steps will be needed:

Verify that the image and categories fields appear as needed on the form at "Structure -> Content Types -> API Doc -> Manage form display".
Verify proper configuration of the API catalog view.