Details
-
Type:
Bug
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 4.6.25, 4.7.15
-
Fix Version/s: None
-
Component/s: CiviCRM API
-
Labels:
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:None
-
Funding Source:Contributed Code
-
Verified?:No
Description
Using repattransaction as a convenience to create a failed contribution doesn't result in a sensible outcome when a membership is involved.
It renews a membership if one is associated with the repeated contribution.
Attachments
Issue Links
- links to
For the record, I'm convinced that this is NOT a good issue and should be dropped.
The outcome is really just a convenience for developers who want to generate failed transactions within a schedule. You can do this safely and relatively easily already with lower level api calls.
The repeattransaction is complex and has had repeated issues, it's doing way, way, way too many things, many of which are not well documented and have built in assumptions (e.g. especially with how memberships are handled).
Adding more functionality here would be a dangerous, unnecessary headache, even though in theory, it sounds like something this function should do.