CiviCRM Community Forums (archive)

I have a problem with a recently completed Drupal7 / Civi4 site. I have an event registration form, with credit card payments handled by PayPal Web Payments Pro. This form was tested extensively prior to launch and was working fine and for 10 days or so after launch. Nothing significant has changed since then  with regard to the server or civi configuration (famous last words!).

Now, when the initial form is submitted (that should go to the confirmation screen), it churns away for 10 seconds or so, and then reloads the same page with no errors, either on the page or in the Apache error log. This was tested in 3 browsers, on 2 different systems. The Apache access log show a simple POST with 200 response code back to the same page (POST /civicrm/event/register HTTP/1.1" 200). It acts like there is a validation error, but no errors show on the screen, none in log, and in fact none anywhere. Many variations on filling out the form, all result in the same behavior.

This form is set up so that the paid items are optional. The event itself is free, but meals, etc have to be paid for. If the same form is submitted with all the paid items set to zero, the form submits fine. So its something related to payment handling.

Can someone please give me some clues how to debug this mysterious error???

Thanks!

I would go about disabling the new line items added and getting it to work

once it is working, reenable the line items one by one and see what breaks it

kinda hard to be more specific

lobo

Hi,

Enable the debug mode if you haven't already. Civi does write to the drupal log too.

X+

I did find some debug log stuff in the Drupal admin stuff, but there is nothing there related to this.

As another test, I created a different price set from scratch with the same items, and it is failing too. Then I think well, follow Lobo's idea, and remove everything except 1 paid item from that price set, and it fails too.

It turns out what was wonky was the profile for this event. The price set issue was a very strange red herring and had nothing to do with the problem.

The root cause of the issue was that there were four fields in this price set that all had their Field Names set to Participant > Contribution. Not sure how they got that way as we had custom data set up for these 4 fields. I stumbled on this when by process of elimination found the profile to be the cause, and started recreating the profile from scratch using the old profile as a template. I added the first field as Participant > Contribution, but civi would only let me add one such field, complaining about 'error adding new item ...blah'. This made me realize that the configuration of the original profile was suspect. Once I paired those 4 fields with the custom data, all was well.

It is still a total mystery how those 4 fields got that way, but it caused all sorts of other wierdness as well (was not able to add any new fields of any kind to this profile at all, I was not able to change any of the labels on these 4 items, one of the four went AWOL and would not show on the form itself though quite clearly was enabled).

Thanks @dlobo  for the help!