You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need a process for synchronizing the version number of the Integration module with Workbench. Workbench's check_integration_module_version() function compares the version of the target Drupal's Integration module (which it fetches via the "IslandoraWorkbenchIntegrationVersionController" REST endpoint) so that Workbench can use new functionality enabled by updates to the target Integration module.
Currently the version number hard coded in Workbench is 1.0. Our problem is that if we change the minor version number of the Integration module (i.e., from 1.0.x to 1.1.x) without updating Workbench, Workbench will cease to work since its check for the current version of the Integration module will fail.
I suggest that we introduce a Workbench configuration setting with a default value of 1.0 (for now) so that users can set it higher if they need to, e.g. to use new features that depend on a later version of the module. We can update this default in Workbench but if users don't want to update Workbench, they can at least adjust the minimum Integration module version back to 1.0 in their configs if they need to.
The text was updated successfully, but these errors were encountered:
mjordan
changed the title
Revert version number from 1.1.0 to 1.0.0 until we have a process for syncing Workbnech
Devise a process for syncing the Integration module's version number with Workbench
Aug 28, 2023
We need a process for synchronizing the version number of the Integration module with Workbench. Workbench's
check_integration_module_version()
function compares the version of the target Drupal's Integration module (which it fetches via the "IslandoraWorkbenchIntegrationVersionController" REST endpoint) so that Workbench can use new functionality enabled by updates to the target Integration module.Currently the version number hard coded in Workbench is 1.0. Our problem is that if we change the minor version number of the Integration module (i.e., from 1.0.x to 1.1.x) without updating Workbench, Workbench will cease to work since its check for the current version of the Integration module will fail.
I suggest that we introduce a Workbench configuration setting with a default value of
1.0
(for now) so that users can set it higher if they need to, e.g. to use new features that depend on a later version of the module. We can update this default in Workbench but if users don't want to update Workbench, they can at least adjust the minimum Integration module version back to 1.0 in their configs if they need to.The text was updated successfully, but these errors were encountered: