Author Topic: Problem with membership when pay later is chosen (Read 894 times)

qjensen · July 15, 2009, 11:16:34 am

I have been working on a system to handle chapters for one of my clients. I have most of it working and members are able to join chapters on the same page where they sign up for membership to the parent org.

The problem I have is if it is a pay later set up, I want to set the join date to null, which is just what CiviCRM does when adding a membership. When I use the Membership API call

Code: [Select]

civicrm_contact_membership_create($mem_params); with join_date set to null or 0, the record never gets added to the db. If I use today's date as the join date, the record gets added correctly. Is this a bug in CiviCRM, or is this the correct behavior?

Thanks for your help,
Quint

lcdweb · July 15, 2009, 12:06:33 pm

try setting it to: 0000-00-00 00:00
(just a guess -- I think the field definition disallows null values)

qjensen · July 15, 2009, 02:24:35 pm

The field def in MySQL has the default value set as null.

If I leave the join_date value out of the params array in the api call or set it to null, the record never gets added. I looked at the API code and it isn't immediately evident why this would be a problem.

I am going to keep digging and I'll post back if I figure it out.

qjensen · July 15, 2009, 02:36:03 pm

OK - I looked at the API code and followed that into the BAO code and found that to have the pay later handled correctly, you must set is_override to 1.

CiviCRM Community Forums (archive)

News:

Author Topic: Problem with membership when pay later is chosen (Read 894 times)

qjensen

Problem with membership when pay later is chosen

lcdweb

Re: Problem with membership when pay later is chosen

qjensen

Re: Problem with membership when pay later is chosen

qjensen

Re: Problem with membership when pay later is chosen