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
The following points are required for a stable release of the module:
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.
Switching from ActiveCampaing Api version 1 to version 3 and using a new php wrapper for communication with this api.
Active
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.