CiviCRM Community Forums (archive)

I've got an issue (surprise!)   

I'm using CiviEvent to register people for courses. it works fine so long as the course is free. when I use the 'paid event' feature it doesn't record the registration, although it:

- debits the registrants credit card (via Paypal web payment standard at the moment)
- sends them back to the payment confirmation page
- records the payment in the CiviContribute
- sends out the confirmation email for their records

The payment shows up in CiviContribute as status: 'completed' but the contact doesn't turn up in the list of 'participants' (to use CiviEvent terminology) for this event.

Attached is a screenshot of the payment confirmation.

Again, if the event doesn't use the 'paid event' feature the contact shows up as an event participant.

now I've tried using the Website Payments Pro instead of Standard. (I've paid for this feature with PayPal and set up the API details accordingly in civicrm.settings.php.

I get this error when sending from the 'confirm details' page to PayPal:


Payment Processor Error message:
10002:Security error Security header is not valid

looked through that thread and many other.

maybe its because I'm not using SSL?

CiviCRM » Administer CiviCRM » Global Settings >> Settings - Payment Processor

gives the option to Force Secure URLs (SSL) but I have that off.

Also i don't have an SSL for this domain. Is it essential?

Is that why I'm getting these errors?

I think what I'm trying to do is pretty straightforward here.

Also is there a URL that I should set PayPal's IPN too?

i have fixed this in trunk. There are still a few remaining issues to fix from:

http://issues.civicrm.org/jira/browse/CRM-2007

Once we have fixed it, we'll figure out if we should backport this issue or not.

The records are actually created, however the is_test field is set to NULL rather than 0

u can fix your db for now by doing:

UPDATE civicrm_participant SET is_test = 0 WHERE is_test is null;

lobo

for now, i'd do it manually on a daily basis or set a cronjob to do this daily

I suspect the next revision release of 1.7 will have the fix once we get a better handle on the other parts of that issue

lobo

Might be easier to upgrade to 1.8 . The fix should be in 1.8

lobo