Upgrade plan for Group 3.x compatibility

Created on 14 March 2023, over 1 year ago
Updated 18 July 2023, over 1 year ago

Problem/Motivation

Issue #1
The group module version we are using is 1.4 but the recommended version is 3.x

We need to plan for upgrading from 1.4 to the 3.x version as EOL is approaching for the 1.x version.

This involves updating the gcommerce suite of modules that make use of the Group module.

As a part of that upgrade the gcommerce modules should be re-written so that the code base uses best practices and up to date methods.

Issue #2
This leads to issue #2 which is to update the gcommerce suite of modules so that permissions set by the group modules are respected. The access handlers need to be updated.

Proposed resolution

The 2.x upgrade changes some class and method names around, so we would likely need to make some changes to gcommerce and custom code. e.g. GroupContent is now GroupRelationship. The underlying machine names are NOT changing, to make 1->2 upgrade fairly painless. (Well…pain free if you used the module with no custom code. Some pain to change the class/method names in cases where you do.)

2->3 upgrades require some DB updates to happen.

The full scope of work needs to be ticketed out into discrete tickets. The purpose of this issue is to document the known needs and next steps.

Feature request
Status

Active

Version

3.0

Component

Code

Created by

🇺🇸United States moxojo

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024