Created on 21 September 2022, almost 2 years ago
Updated 17 October 2023, 9 months ago

Problem/Motivation

After investigating the custom yaml mapping bug, I have come to the conclusion that the fault lies with the php api wrapper being used. Since it only works on the ActiveCampaing api version 1 which is oudated and the wrapper is also no longer maintained, I decided to write out a roadmap for a stabel release of the ActiveCampaing module in 2.0

Proposed resolution

The following points are required for a stable release of the module:

  1. Make the module D10 compatible: When rolling out a new stable version, the module should be D10 compatible.
  2. Switch to ActiveCampaing api version 3: In the new release, we will use the new and supported version of the ActiveCampaing api.
  3. Replace the old php wrapper with a new one: Testing which other packagist active campaign api wrapper can be used to communicate with the ActiveCampaing api version 3.
  4. Fix the custom yaml mapping: As mentioned above, the custom yaml mapping should work after switching to a new wrapper, test this and mark it as a feature on the project page.
  5. After switching API version, also provide testing for all API calls. To make the module more stable.
  6. Add the module to the Drupal security advisory policy: Make sure the module is security advisory policy ready.

Remaining tasks

  • Adjust all API calls to work with the ActiveCampaing Api version 3 and test thoroughly.
  • Test other wrappers and decide which one works best.
  • Fix problems with the custom yaml mapping if there are any and test if all data is send correctly to ActiveCampaing
  • Provide test coverage for the api calls.
  • Focus on good coding standards to allow for Drupal security advisory coverage.
  • Make a stable release from the 2.0 branch.
  • Opt-in to the security advisory policy.

User interface changes

I would like to limit the UI changes, to allow switching from version 1 to version 2 to go unnoticed by the users of the module (the site webmasters).

In case of unavoidable UI changes due to the modifications, this will be mentioned here.

API changes

Switching from ActiveCampaing Api version 1 to version 3 and using a new php wrapper for communication with this api.

πŸ“Œ Task
Status

Active

Version

2.0

Component

Code

Created by

πŸ‡§πŸ‡ͺBelgium dtfabio Ninove

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.69.0 2024